CVE-2023-30997
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM 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: 254638.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIBM Security Access Manager Docker versions 10.0.0.0 through 10.0.7.1 contains a local privilege escalation vulnerability where improper access controls allow a local unprivileged user to gain root access to the container environment.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 10.0.0.0, <= 10.0.7.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify IBM Security Access Manager Docker containerRun 'docker ps' or inspect the container environment to confirm the image name contains 'IBM Security Access Manager' or 'isam'Affected if The container is running an IBM Security Access Manager Docker image
-
Check installed versionInside the container, run a command to display the ISAM version (e.g., 'grep version', check /opt/IBM directory, or use any available version query command). Compare the output to the affected range 10.0.0.0 through 10.0.7.1Affected if The version number falls within 10.0.0.0 to 10.0.7.1 inclusive
-
Inspect container user configurationRun 'docker exec <container> id' or 'cat /etc/passwd' inside the container to identify which users exist and their privilege levels. Check for non-root users that should not have elevated accessAffected if Unprivileged users exist in the container who should not have access to sensitive resources
-
Review file permissions on sensitive directoriesRun 'ls -la' on directories such as /opt/IBM, /var, or any configuration directories inside the container. Check if files or scripts are writable by non-root usersAffected if Sensitive files or scripts are writable by unprivileged users, enabling privilege escalation
-
Check for improper access control configurationsInspect configuration files related to user roles, permissions, or access control policies inside the container. Look for misconfigured settings that grant excessive permissionsAffected if Access control configurations permit unprivileged users to modify system files or execute privileged operations
A user is affected if they are running IBM Security Access Manager Docker version 10.0.0.0 through 10.0.7.1 with unprivileged users present or improper file permissions that could enable local privilege escalation to root.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a patched version of IBM Security Access Manager Docker beyond 10.0.7.1, or apply vendor-supplied access control fixes. Review and harden file permissions and user role configurations within the container.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30997 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-30997 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data