Cross-environment data exposure via Git cache collisions
Published Sep 5, 2023 · Updated Feb 13, 2025
Cache isolation failure in Salt masters before 3005.2 or 3006.0 through 3006.1 allows local users to read or execute data from another Git environment. The gitfs cachedir_basename calculation omits environment-specific information, so distinct environments using the same repository can share a cache directory; inadequate locking also permits races. Exposure requires Git Providers configured with different environments and can disclose unintended data, run the wrong content, corrupt data, or crash a consumer.
Summary
What happened
Cache isolation failure in Salt masters before 3005.2 or 3006.0 through 3006.1 allows local users to read or execute data from another Git environment. The gitfs cachedir_basename calculation omits environment-specific information, so distinct environments using the same repository can share a cache directory; inadequate locking also permits races. Exposure requires Git Providers configured with different environments and can disclose unintended data, run the wrong content, corrupt data, or crash a consumer.
The record
- CVE
- CVE-2023-20898
- Published
- Sep 5, 2023
- Updated
- Feb 13, 2025
- Vendor
- Salt Project
- Product
- Salt
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 5, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 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=Salt masters prior to 3005.2 or 3006.2
What conditions does exploitation require?
What is affected?
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
No sourced classifications are available.
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