Security Resilience

CVE-2023-38369

Ibm Security Access Manager Container 10.0.0.0 – 10.0.6.1

Published
07 February 2024
Modified
03 November 2025
Patch / advisory
CVSS Score v3.1 6.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0053 46th percentile
Risk Priority 48 floored blend · peak EPSS

CVSS 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

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

T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
T1110.001 Password Guessing Credential Access
Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts.
T1110.002 Password Cracking Credential Access
Adversaries may use password cracking to attempt to recover usable credentials, such as plaintext passwords, when credential material such as password hashes are obtained.
T1110.003 Password Spraying Credential Access
Adversaries may use a single or small list of commonly used passwords against many different accounts to attempt to acquire valid account credentials.
T1558.003 Kerberoasting Credential Access
Adversaries may abuse a valid Kerberos ticket-granting ticket (TGT) or sniff network traffic to obtain a ticket-granting service (TGS) ticket that may be vulnerable to [Brute Force](https://attack.
T1584.006 Web Services Resource Development
Adversaries may compromise access to third-party web services that can be used during targeting.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-31002Same product: Ibm Security Access Manager Container
CVE-2024-40684Same vendor: Ibm
CVE-2023-50305Same vendor: Ibm
CVE-2025-1993Same vendor: Ibm
CVE-2024-22355Same vendor: Ibm
CVE-2024-41778Same vendor: Ibm
CVE-2023-37398Same vendor: Ibm
CVE-2024-40697Same vendor: Ibm
CVE-2024-22330Same vendor: Ibm
CVE-2023-49883Same vendor: Ibm

Affected Assets

ibm
security access manager container
10.0.0.0 — 10.0.6.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 2 hardening rules · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)
  • V6.2.4
  • V6.2.12
  • V6.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.

PR.AA-03 full match
blocks

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.

removes

A.5.17 mandates strong password requirements, so applying it to a system that previously lacked them removes the weakness by imposing the requirement.

finds

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.

finds

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.

blocks

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.

blocks

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.

blocks

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

References