CVE-2023-26271
Ibm Guardium Cloud Key Manager ≤ 1.10.3
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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-26271 is a medium-severity Improper Restriction of Excessive Authentication Attempts (CWE-307) vulnerability in Ibm Guardium Cloud Key Manager. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Brute Force (T1110); ranked at the 42th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-30094
Vulnerability Data
IBM Security Guardium Data Encryption (IBM Guardium Cloud Key Manager (GCKM) 1.10.3)) uses an inadequate account lockout setting that could allow a remote attacker to brute force account credentials. IBM X-Force ID: 248126.
- 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
—
Likely Mitigating Controls
Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
This control directly enforces limits on consecutive invalid logon attempts and automatic response (e.g., lockout) to prevent brute-force exploitation of authentication mechanisms.
Specific conditions can include excessive failed attempts, triggering stronger authentication that restricts brute-force exploitation.
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.
Authentication enforcement directly includes lockout, throttling, and MFA policies that prevent brute-force attempts.
Behavioral monitoring of authentication activity can detect excessive failed attempts after they occur.
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.
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.
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.
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.
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.
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.
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