Private-key disclosure via world-readable temporary file
Published Jan 11, 2024 · Updated Nov 3, 2025
Information disclosure in IBM Security Verify Access 10.0.0.0 through 10.0.6.1 allows local users to read private keys from temporary files. The build_health_check_config function in /usr/sbin/bootstrap.sh exports DSC server and client keys to predictable /tmp/health_check.p12 under the default 022 umask. Local access to the container during instance startup is required, and disclosure is limited to the exported private keys.
Summary
What happened
Information disclosure in IBM Security Verify Access 10.0.0.0 through 10.0.6.1 allows local users to read private keys from temporary files. The build_health_check_config function in /usr/sbin/bootstrap.sh exports DSC server and client keys to predictable /tmp/health_check.p12 under the default 022 umask. Local access to the container during instance startup is required, and disclosure is limited to the exported private keys.
The record
- CVE
- CVE-2023-31001
- Published
- Jan 11, 2024
- Updated
- Nov 3, 2025
- Vendor
- IBM
- Product
- IBM Security Verify Access Appliance
- Classifications
- CWE-257, T1552.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 11, 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.0 <=10.0.6.1
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
- Private-key extraction race demonstrationproof of concept · demonstrated
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