dbcve.org
Security Verify Access DockerApplication · Ibm

CVE-2024-35141

HIGH · 7.8 CVSS v3.1 Published 2024-12-19
Fix available
A fix is available. Upgrade to after 10.0.7 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
IBM Security Verify Access Docker 10.0.0 through 10.0.6 could allow a local user to escalate their privileges due to execution of unnecessary privileges.

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 · moderate confidence

IBM Security Verify Access Docker versions 10.0.0 through 10.0.6 contains a local privilege escalation vulnerability where the application or container runs with unnecessary system privileges, allowing a local authenticated user to leverage those excess privileges to gain higher-level access on the host system.

MitigationUpdate IBM Security Verify Access Docker to version 10.0.7 or later to obtain the patched version. Additionally, review and apply least-privilege principles to container execution, ensuring the container runs with minimal required capabilities and does not run as root unless absolutely necessary.

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
Security Verify Access DockerApplication
Affected:>= 10.0.0, <= 10.0.7

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify IBM Security Verify Access Docker version
    Run 'docker images' to list all Docker images and look for the IBM Security Verify Access image. Use 'docker inspect <image_id>' or check image tags to determine the exact version number installed.
    Affected if The installed version is between 10.0.0 and 10.0.7 inclusive.
  2. Check if container runs as root user
    Run 'docker inspect <container_name_or_id>' and look for the 'User' field in the 'Config' or 'HostConfig' section. Alternatively, execute 'docker exec <container> id' to see the effective user ID inside the running container.
    Affected if The container runs as root (UID 0) or the User field is empty/default.
  3. Check container capability set
    Run 'docker inspect <container_name_or_id>' and examine the 'CapAdd' and 'CapDrop' fields in the 'HostConfig' section. Also use 'docker exec <container> capsh --print' inside the container to list current capabilities.
    Affected if The container has excessive capabilities (such as CAP_SYS_ADMIN) or CAP_SYS_ADMIN is present in the capability set.
  4. Check if container runs in privileged mode
    Run 'docker inspect <container_name_or_id>' and look for the 'Privileged' field in the 'HostConfig' section.
    Affected if The 'Privileged' field is set to true.

A user is affected if their IBM Security Verify Access Docker version is 10.0.0 through 10.0.7 AND the container runs with root user, elevated capabilities, or in privileged mode.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 10.0.7
Interim mitigation

Update IBM Security Verify Access Docker to version 10.0.7 or later to obtain the patched version. Additionally, review and apply least-privilege principles to container execution, ensuring the container runs with minimal required capabilities and does not run as root unless absolutely necessary.

Recommended fix Moderate confidence

IBM Security Verify Access Docker 10.0.8 or later

  1. Identify the current IBM Security Verify Access Docker version in use by checking the container image tag or running `docker images`
  2. Stop any running containers based on the affected versions (10.0.0 through 10.0.7)
  3. Remove the vulnerable container images from the local registry: `docker rmi <image-id>`
  4. Pull the fixed version of IBM Security Verify Access Docker (10.0.8 or later) from the official IBM container registry
  5. Deploy the new container image following your standard deployment procedures
  6. Verify the container is running correctly and the application is functional
  7. Confirm the new version is applied by checking the container image: `docker images`
Caveat Review IBM's release notes for 10.0.8+ to check for any configuration or API changes that may affect existing deployments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Security Verify Access Docker Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-35141 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-35141 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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