Security Resilience

CVE-2023-31005

LPE in Ibm Security Verify Access 10.0.0.0 – 10.0.6.1

Published
03 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.0023 14th percentile
Risk Priority 46 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-31005 is a medium-severity Improper Privilege Management (CWE-269) vulnerability in Ibm Security Verify Access. Its CVSS base score is 6.2 (Medium).

Operationally, ranked at the 14th 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 AC-2 (Account Management) and AC-24 (Access Control Decisions) — 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 (IBM Security Verify Access Appliance 10.0.0.0 through 10.0.6.1 and IBM Security Verify Access Docker 10.0.0.0 through 10.0.6.1) could allow a local user to escalate their privileges due to an improper security configuration. IBM X-Force ID:…

more

254767.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-31004Same product: Ibm Security Verify Access
CVE-2024-43187Same product: Ibm Security Verify Access
CVE-2023-31001Same product: Ibm Security Verify Access
CVE-2024-35133Same product: Ibm Security Verify Access
CVE-2024-45647Same product: Ibm Security Verify Access
CVE-2023-43016Same product: Ibm Security Verify Access
CVE-2024-40700Same product: Ibm Security Verify Access
CVE-2023-32327Same product: Ibm Security Verify Access
CVE-2023-32329Same product: Ibm Security Verify Access
CVE-2023-31003Same product: Ibm Security Verify Access

Affected Assets

ibm
security verify access
10.0.0.0 — 10.0.6.1
ibm
security verify access docker
10.0.0.0 — 10.0.6.1

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Account management directly governs assignment and tracking of privileges so proper implementation stops the weakness from being introduced.

Requiring explicit access-control decisions ensures privileges are evaluated rather than assumed or omitted.

Access enforcement applies the correct privilege checks at every request, structurally preventing unintended spheres of control.

Separation of duties constrains how privileges may be assigned, reducing the chance of overly broad actor control.

Least privilege is the direct countermeasure to improper privilege management; implementing it eliminates the root cause.

Binding security attributes to subjects/objects supplies the mechanism needed to track and enforce privileges correctly.

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.

blocks

A.8.2 directly controls the identification, allocation, review, expiry, temporary use, and separation of privileged rights per policy, which prevents most improper privilege management (CWE-269) by design; the bounded remainder is flawed tracking/checking logic inside the product's own enforcement code (the AC-3 slice of 269).

blocks

A.8.3's access restriction mechanisms (per-identity rights, dynamic access management, isolation) block exploitation of improperly assigned privileges when the mis-assignment sits in a layer A.8.3's own authorization decisions override, but many CWE-269 instances are the access control itself being wrong (role definitions, self-grant, setuid programs, privilege-not-reset), where A.8.3 IS the defective layer and cannot block its own failure.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

References