Cyber Resilience

CVE-2023-30998

LPE in Ibm Security Access Manager 10.0.0.0 – 10.0.7.1

Published
27 June 2024
Modified
03 November 2025
Patch / advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0023 14th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2023-30998 is a high-severity Execution with Unnecessary Privileges (CWE-250) vulnerability in Ibm Security Access Manager. Its CVSS base score is 7.8 (High).

Operationally, ranked at the 14th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

IBM Security Access Manager Docker 10.0.0.0 through 10.0.7.1 could allow a local user to obtain root access due to improper access controls. IBM X-Force ID: 254649.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-30997Same product: Ibm Security Access Manager
CVE-2023-38368Same product: Ibm Security Access Manager
CVE-2024-35139Same product: Ibm Security Access Manager
CVE-2024-35137Same product: Ibm Security Access Manager
CVE-2023-38371Same product: Ibm Security Access Manager
CVE-2023-38370Same product: Ibm Security Access Manager
CVE-2024-31890Same vendor: Ibm
CVE-2024-49814Same vendor: Ibm
CVE-2025-36356Same vendor: Ibm
CVE-2025-33120Same vendor: Ibm

Affected Assets

ibm
security access manager
10.0.0.0 — 10.0.7.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 6 hardening rules · 6 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V10.2.3
  • V13.2.2

Likely Mitigating Controls AI

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.

addresses: CWE-250

Policy promotes least privilege by defining necessary privileges and management commitment to them.

addresses: CWE-250

Supervision detects and allows removal of unnecessary privileges that enable execution with excess rights.

addresses: CWE-250

Reviewing accounts for compliance, disabling/removing unneeded accounts, and aligning with termination processes prevents execution with unnecessary privileges.

addresses: CWE-250

Separation of duties prevents any single user from holding all privileges needed to complete a critical task, directly reducing execution with unnecessary privileges.

addresses: CWE-250

Directly prevents execution with more privileges than needed for assigned tasks.

addresses: CWE-250

Role-based training on least privilege principles reduces the chance personnel assign or retain unnecessary privileges.

addresses: CWE-250

Analysis of audit records can identify execution with unnecessary privileges through unusual activity patterns.

addresses: CWE-250

Automatic termination after a defined period eliminates unnecessary privileges from persistent connections.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 mostly match
prevents

PR.AA-05 directly enforces least privilege so largely eliminates CWE-250 at design time, yet the weakness can still arise from runtime escalation paths, third-party code, or misapplied role definitions outside this single control.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Requiring explicit justification and time-limited grants discourages the routine allocation of unnecessary privileges that would otherwise allow execution with more rights than required.

prevents

Restricting privileged utilities to the fewest trusted users and requiring explicit authorization directly stops developers or operators from embedding or invoking code that runs with unnecessary elevated rights.

prevents

Mandating separate non-privileged identities for routine work and restricting privileged accounts to administrative tasks reduces the chance that everyday operations run with unnecessary elevated rights.

prevents

The control explicitly calls for minimizing privileged identities and disabling unnecessary accounts, thereby reducing the number of processes that run with unnecessary privileges.

prevents

The requirement to restrict privileged access and apply segregation of duties limits the number of processes or accounts that must run with elevated rights, lowering the impact of unnecessary privilege assignments.

mitigates

Forcing distinct roles for initiating versus executing changes reduces the chance that an individual will run with unnecessary privileges to perform both steps.

References