CVE-2023-38369
Ibm Security Access Manager Container 10.0.0.0 – 10.0.6.1
Raw vector
CVSS:3.1/AV:L/AC:L/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-38369 is a medium-severity Weak Password Requirements (CWE-521) vulnerability in Ibm Security Access Manager Container. Its CVSS base score is 6.2 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Brute Force (T1110); ranked at the 46th 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.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-42186
Vulnerability Data
IBM Security Access Manager Container 10.0.0.0 through 10.0.6.1 does not require that docker images should have strong passwords by default, which makes it easier for attackers to compromise user accounts. IBM X-Force ID: 261196.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 1 OS baseline
V6.2.4V6.2.12V6.4.1
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
IA-5 directly requires organizations to enforce strength, complexity, and change rules for passwords and other authenticators at issuance and reset.
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.
Explicitly requires enforcing minimum password strength as part of authentication.
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 mandates strong password requirements, so applying it to a system that previously lacked them removes the weakness by imposing the requirement.
A.8.29's programme explicitly covers authentication functions (8.5) and includes code review, SAST, DAST and penetration testing — all of which reach CWE-521 from both source (missing/weak password validation logic) and runtime (trying 'password123' at registration). The remainder is bounded and nameable: policies that exist but are subtly weak (e.g., allow 'Password1' but block 'password'), or are enforced inconsistently across entry points, which a single test cycle may not fully characterise.
A.5.21's supplier security requirements and validation methods can surface weak password requirements in acquired ICT products, but it does not systematically reach internally developed or legacy deployed software, so it finds only a minority of instances.
Training makes users aware of password-strength expectations and motivates stronger choices, but because the product still does not enforce strong passwords, any untrained or noncompliant user can set a weak password that remains exploitable.
A.6.7 guidance item (k) requires secure authentication mechanisms for remote access, explicitly calling out the vulnerability of single-factor authentication; a well-implemented control would mandate multi-factor authentication for remote access, which blocks exploitation of weak passwords in that context, but the weakness remains exploitable via local network access, other services, and any non-remote authentication paths.
A.8.21 item (b) covers authentication requirements for accessing network services, which can include password strength requirements, blocking exploitation of weak passwords on those services; the remainder is bounded and nameable -- passwords for non-network-service contexts (local accounts, application logins, etc.) are outside the clause's scope, mirroring the A.8.20 -> CWE-523 partial pattern where the control covers part of the surface.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over our cross-walk; rows rated `none` are excluded, and each rule says how its mapping was checked.
Definition changed on 29 October 2026. Until then this section listed every rule rated above none, partial included. From that date it lists rules whose mapping is rated full or mostly and checked at llm_unverified or higher; partial mappings show when you ask.
No rule maps to these weaknesses at full or mostly. Tick the option above to see the partial mappings.
RHEL 7 (2 partial rules)
- V-204424 The Red Hat Enterprise Linux operating system must not allow accounts configured with blank or null passwords. blocks CWE-521
- V-204425 The Red Hat Enterprise Linux operating system must be configured so that the SSH daemon does not allow authentication using an empty password. blocks CWE-521