CVE-2024-35140
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 Verify Access Docker 10.0.0 through 10.0.6 could allow a local user to escalate their privileges due to improper certificate validation. IBM X-Force ID: 292416.
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 confidenceIBM Security Verify Access Docker versions 10.0.0 through 10.0.6 contains a local privilege escalation vulnerability stemming from improper certificate validation. A local authenticated user can exploit this to gain elevated privileges. The vulnerability has a CVSS base score of 7.8 (HIGH).
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, < 10.0.7CVSS 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 Verify Access Docker image versionRun 'docker images' to list all Docker images. Look for images with repository name containing 'ibm/security-verify-access' or similar IBM Verify Access patterns. Note the IMAGE ID or TAG for the next step.Affected if The image tag shows a version between 10.0.0 and 10.0.6 inclusive
-
Inspect the exact container image versionRun 'docker inspect <image_id>' or 'docker inspect ibm/security-verify-access:<tag>' to retrieve detailed metadata. Look for version labels or environment variables that specify the exact IBM Security Verify Access version.Affected if The inspected version falls within the range 10.0.0 to 10.0.6
-
Confirm Docker is running IBM Security Verify AccessRun 'docker ps' to list running containers. Identify containers running IBM Security Verify Access by image name or configured container name. Note the container ID for configuration inspection.Affected if A container named or based on IBM Security Verify Access is currently running with an affected version
-
Check for local authenticated user accessReview system user accounts and Docker group membership on the host. Run 'getent group docker' to check Docker group users. Run 'cat /etc/passwd' to enumerate local users who could potentially authenticate to the Docker environment.Affected if Multiple local users exist with access to the Docker daemon or the affected container, creating conditions for local privilege escalation exploitation
-
Review certificate validation configurationExamine Docker container configuration and any mounted certificate files or volumes. Check if custom certificate validation scripts or configurations exist in the container environment. Inspect mounted paths for certificate-related files using 'docker inspect <container_id>' to view mounts.Affected if Custom or non-default certificate validation is configured, indicating the improper validation condition may be present
You are affected if the Docker image version of IBM Security Verify Access is between 10.0.0 and 10.0.6 inclusive and local authenticated users have access to the Docker environment.
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.
dbcve · scoped10.0.7
Upgrade IBM Security Verify Access Docker to a version beyond 10.0.6. If immediate patching is not feasible, restrict local user access to the Docker environment and monitor for unauthorized certificate manipulation.
10.0.7
- 1. Back up the current IBM Security Verify Access Docker container configuration and any persistent data volumes
- 2. Pull the fixed Docker image: docker pull <image-name>:10.0.7 (replace <image-name> with the actual IBM Security Verify Access image name)
- 3. Stop the currently running container: docker stop <container-name>
- 4. Remove the old container: docker rm <container-name>
- 5. Deploy the new container using the 10.0.7 image with the same configuration parameters used for the previous version
- 6. Verify the container is running correctly: docker ps
- 7. Confirm the upgrade by checking the version inside the container or via the admin interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.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,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35140 — 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-2024-35140 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