CVE-2023-31001
Ibm Security Verify Access 10.0.0.0 – 10.0.0.7
Raw vector
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-31001 is a medium-severity Storing Passwords in a Recoverable Format (CWE-257) vulnerability in Ibm Security Verify Access. Its CVSS base score is 5.1 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked at the 11th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to IA-5 (Authenticator Management) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-35339
Vulnerability Data
IBM Security Access Manager Container (IBM Security Verify Access Appliance 10.0.0.0 through 10.0.6.1 and IBM Security Verify Access Docker 10.0.6.1) temporarily stores sensitive information in files that could be accessed by a local user. IBM X-Force ID: 254653.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V11.4.2V11.4.4
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
IA-5 requires proper management of authenticators including storage of passwords only in non-recoverable (hashed) form, directly stopping the weakness from existing.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
A.5.17's password management system section mandates that passwords be stored in protected form (h) and that password encryption and hashing be performed according to approved cryptographic techniques, which directly addresses CWE-257's recoverable-format storage; applied to a system that previously stored passwords reversibly, the implementation requires re-hashing with approved one-way techniques, so the weakness stops being present with no nameable remainder.
A.8.29's SOURCE reach (code review, static analysis) directly inspects the password-handling code where the reversible-encryption/compression/cleartext choice is made, and its RUNTIME reach (penetration testing) sees the format if the store is dumped; the remainder is third-party components outside the developer's source and custom reversible schemes that evade static rules.
A.5.15 mandates implementation of access control rules that restrict who can reach the password store, blocking exploitation by unauthorized users; however, the recoverable-format weakness itself is unchanged, and authorized insiders (e.g. administrators with legitimate access to the credential store) can still recover and reuse passwords — the threat the CWE description explicitly names — so the control masks the vulnerability for a portion of the threat surface but does not address the underlying flaw.
A well-implemented cryptography policy under A.8.24 can specify approved practices for credential storage (e.g., requiring one-way hashing rather than reversible encryption, and disallowing reversible compression as a password verifier), which prevents some instances of CWE-257; however, the clause's primary mechanism is encryption for confidentiality/integrity, not authentication-credential storage, so coverage is limited to what the topic-specific policy chooses to address.
Secure coding practices can prevent developers from implementing recoverable password storage.
A.8.3 restricts who can reach the password store, blocking external attackers from exploiting the recoverable format, but the CWE explicitly names the insider threat (system administrators with legitimate access can still recover passwords), and access restriction does not stop those with authorized read access from exploiting the recoverability.