Security Resilience

CVE-2023-38273

Ibm Cloud Pak System 2.3.3.0 – 2.3.3.6

Published
02 February 2024
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0067 53th percentile
Risk Priority 58 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-38273 is a high-severity Improper Restriction of Excessive Authentication Attempts (CWE-307) vulnerability in Ibm Cloud Pak System. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Brute Force (T1110); ranked in the top 47% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-7 (Unsuccessful Logon Attempts) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM Cloud Pak System 2.3.1.1, 2.3.2.0, and 2.3.3.7 uses an inadequate account lockout setting that could allow a remote attacker to brute force account credentials. IBM X-Force ID: 260733.

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.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.
T1110.004 Credential Stuffing Credential Access
Adversaries may use credentials obtained from breach dumps of unrelated accounts to gain access to target accounts through credential overlap.
T1584.006 Web Services Resource Development
Adversaries may compromise access to third-party web services that can be used during targeting.
T1586 Compromise Accounts Resource Development
Adversaries may compromise accounts with 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-38716Same product: Ibm Cloud Pak System
CVE-2023-38713Same product: Ibm Cloud Pak System
CVE-2023-38714Same product: Ibm Cloud Pak System
CVE-2023-38271Same product: Ibm Cloud Pak System
CVE-2026-3295Same product: Ibm Cloud Pak System
CVE-2023-38007Same product: Ibm Cloud Pak System
CVE-2025-2895Same product: Ibm Cloud Pak System
CVE-2023-38012Same product: Ibm Cloud Pak System
CVE-2023-38013Same product: Ibm Cloud Pak System
CVE-2023-38265Same product: Ibm Cloud Pak System

Affected Assets

ibm
cloud pak system
2.3.1.1, 2.3.2.0, 2.3.3.7 · 2.3.3.0 — 2.3.3.6

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)

—

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

AC-7 directly enforces limits on consecutive failed logons, structurally blocking brute-force exploitation of the weakness.

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 mostly match
blocks

Authentication enforcement directly includes lockout, throttling, and MFA policies that prevent brute-force attempts.

DE.CM-03 partial match
blocks

Behavioral monitoring of authentication activity can detect excessive failed attempts after they occur.

PR.PS-04 partial match
blocks

Generating auth logs enables later detection or forensics but does not itself restrict attempts.

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.8.5 directly mandates protection against brute force log-on attempts, so implementing it removes the absence of such restrictions that constitutes CWE-307.

finds

A.8.29's combined programme of code review, static analysis, and penetration testing reaches CWE-307 through both SOURCE (missing rate-limiting/lockout logic is visible in authentication code) and RUNTIME (pentesting directly exercises brute-force resistance); the remainder is bounded and nameable — subtle design flaws where rate limiting exists but is bypassable under specific conditions, which a single test cycle may not surface.

prevents

Training can make developers aware that authentication endpoints need rate limiting and account lockout, reducing some instances of this architectural omission, but it is a fallible human practice against a design/code defect — the same reasoning as A.6.3 -> CWE-598 and AT-2 -> CWE-79.

prevents

A.8.28's secure design/architecture and threat-modelling guidance would lead a developer to implement rate limiting or account lockout, but the clause mandates a practice rather than a specific authentication-throttling mechanism, so what it catches depends on the rigour of implementation — consistent with the partial rungs on CWE-502 and CWE-79.

prevents

A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-307 is an architectural/design weakness in authentication that secure design and threat modeling would address, but the clause's mechanism is contractual and depends on the supplier's implementation, leaving a nameable remainder.

finds

A.8.8's reach is DISCLOSURE — it finds CWE-307 instances only where they carry a vendor-published advisory. CWE-307 commonly surfaces as CVEs (multiple examples in the entry), so the disclosed share is real, but the majority of latent instances are first-party authentication designs that lack rate limiting and are never published as advisories; A.8.8's scanning and inventory reach does not see those.

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.

RHEL 7 (2 rules)
  • V-204427 The Red Hat Enterprise Linux operating system must be configured to lock accounts for a minimum of 15 minutes after three unsuccessful logon attempts within a 15-minute timeframe. blocks CWE-307
  • V-204428 The Red Hat Enterprise Linux operating system must lock the associated account after three unsuccessful root logon attempts are made within a 15-minute period. blocks CWE-307

References