CVE-2023-23382
Microsoft Azure Machine Learning 3.0.0 – 3.0.02076.0001
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-23382 is a medium-severity Storing Passwords in a Recoverable Format (CWE-257) vulnerability in Microsoft Azure Machine Learning. Its CVSS base score is 6.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked in the top 15% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
This vulnerability is AI-related — categorised as Other AI Platforms.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-27482
Vulnerability Data
Azure Machine Learning Compute Instance Information Disclosure Vulnerability
- CWE(s)
AI Security AnalysisAI
- AI Category
- Other AI Platforms
- Risk Domain
- N/A
- OWASP Top 10 for LLMs 2025
- None mapped
- Classification Reason
- Matched keywords: machine learning
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V11.4.2V11.4.4
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.5.17's password management system requirements (h: store/transmit in protected form; approved crypto per 8.24; no recoverable formats implied by strong practices) stop exploitation of recoverable storage for most cases, but the remainder (non-password auth info or systems outside the password management system) is nameable.
Requires proper use of cryptography, which can mitigate recoverable storage if applied correctly to passwords.
A.8.25 requires that security be designed and implemented in the SDLC (including secure coding, requirements, testing and training), but does not itself stop a recoverable-format password from being written into the product or stop that stored password from being exploited afterwards
A.8.26 only requires that recoverable-format storage be identified as a risk and specified as a requirement; it does not itself mandate, design or implement non-recoverable storage, so the flaw (passwords stored in recoverable form) can still exist after the control is satisfied.