🛡️ CVE-2023-35625 — azure-machine-learning-software-developm

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is high, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity none, availability none.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

• Attack vector: Local — a local account, shell or session on the host is needed.
• Attack complexity: High — the attacker first has to win a race, learn a secret or otherwise prepare the target.
• Privileges required: Low — an ordinary user account is enough.
• User interaction: None — nobody has to be tricked into anything.
• Scope: Unchanged — the damage stays inside the vulnerable component.
• Confidentiality impact: High — total loss, or loss the attacker controls.
• Integrity impact: None.
• Availability impact: None.

Weakness class

CVE-2023-35625 is classified as CWE-200: Exposure of Sensitive Information. Information that should stay internal is disclosed to someone who is not authorised to see it.

Affected software

CVE-2023-35625 is recorded against 2 packages.

• azure-machine-learning-software-development-kit (fixed in 1.5.0)
• mltable (fixed in 1.5.0)

Timeline and source

Published on 12 December 2023 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

msrc.microsoft.com
msrc.microsoft.com

Same weakness in other software

These advisories are the same class of weakness (CWE-200: Exposure of Sensitive Information) in other software:

• CVE-2023-41050 (6.8 Medium, published 13 Jul 2026)
• CVE-2022-24886 (2.0 Low, published 12 Jul 2026)
• CVE-2023-30776 (published 7 Jul 2026)
• CVE-2014-3517 (published 6 Jul 2026)
• CVE-2015-9543 (2.0 Low, published 6 Jul 2026)
• CVE-2015-8749 (published 6 Jul 2026)
• CVE-2016-3954 (published 6 Jul 2026)
• CVE-2015-1851 (published 6 Jul 2026)

Details

Affected Packages

References