Local sensitive-information disclosure via temporary files
Published Feb 7, 2024 · Updated Nov 3, 2025
Cleartext storage in IBM Security Verify Access Appliance and Docker 10.0.0.0 through 10.0.6.1 allows local users to read sensitive files. IBM identifies temporary files as the storage locus but has not disclosed which data is written, the file paths, or the access-control error. Local access to an affected appliance or Docker host is required, and the reported consequence is disclosure without modification or service interruption.
Summary
What happened
Cleartext storage in IBM Security Verify Access Appliance and Docker 10.0.0.0 through 10.0.6.1 allows local users to read sensitive files. IBM identifies temporary files as the storage locus but has not disclosed which data is written, the file paths, or the access-control error. Local access to an affected appliance or Docker host is required, and the reported consequence is disclosure without modification or service interruption.
The record
- CVE
- CVE-2023-31002
- Published
- Feb 7, 2024
- Updated
- Nov 3, 2025
- Vendor
- IBM
- Product
- IBM Security Verify Access Appliance
- Classifications
- CWE-312, CWE-256, T1552.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 7, 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
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