Local root escalation via predictable health-check paths
Published May 31, 2024 · Updated Nov 3, 2025
Local privilege escalation in IBM Security Verify Access Docker 10.0.0 through 10.0.6 allows local users to overwrite files as root. The root-run /usr/sbin/health_check.sh writes curl output and errors to predictable /tmp paths and follows attacker-created symbolic links. Access inside an affected container is required, and successful exploitation permits arbitrary root-level file overwrite without a direct availability impact.
Summary
What happened
Local privilege escalation in IBM Security Verify Access Docker 10.0.0 through 10.0.6 allows local users to overwrite files as root. The root-run /usr/sbin/health_check.sh writes curl output and errors to predictable /tmp paths and follows attacker-created symbolic links. Access inside an affected container is required, and successful exploitation permits arbitrary root-level file overwrite without a direct availability impact.
The record
- CVE
- CVE-2024-35140
- Published
- May 31, 2024
- Updated
- Nov 3, 2025
- Vendor
- IBM
- Product
- IBM Security Verify Access Docker
- Classifications
- CWE-295, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 31, 2024CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0.0 <=10.0.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo