Rank-file disclosure or tampering via insecure temporary path
Published Mar 24, 2022 · Updated Aug 2, 2024
Insecure temporary-file creation in Horovod before 0.24.0 allows local users to read or alter an LSF jsrun rank file. The generate_jsrun_rankfile function calls tempfile.mktemp(), then opens the returned path separately, leaving a race in which another process can claim or redirect it. Exposure requires an LSF job using jsrun without binding_args; MPI, Gloo, Spark, and Ray runs are unaffected.
Summary
What happened
Insecure temporary-file creation in Horovod before 0.24.0 allows local users to read or alter an LSF jsrun rank file. The generate_jsrun_rankfile function calls tempfile.mktemp(), then opens the returned path separately, leaving a race in which another process can claim or redirect it. Exposure requires an LSF job using jsrun without binding_args; MPI, Gloo, Spark, and Ray runs are unaffected.
The record
- CVE
- CVE-2022-0315
- Published
- Mar 24, 2022
- Updated
- Aug 2, 2024
- Vendor
- Linux Foundation
- Product
- Horovod
- Classifications
- CWE-668, CWE-377
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 24, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record 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=unspecified <0.24.0
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