Configuration overwrite via .osc source-name collision
Published Oct 16, 2024 · Updated Oct 31, 2024
Configuration overwrite in osc allows local attackers to alter a victim's client settings through crafted package sources. osc places downloaded package sources beside reserved .osc metadata, so a source named _apiurl collides with and replaces the client configuration file. The victim must check out or update the attacker's package; the change can redirect or otherwise modify subsequent osc operations.
Summary
What happened
Configuration overwrite in osc allows local attackers to alter a victim's client settings through crafted package sources. osc places downloaded package sources beside reserved .osc metadata, so a source named _apiurl collides with and replaces the client configuration file. The victim must check out or update the attacker's package; the change can redirect or otherwise modify subsequent osc operations.
The record
- CVE
- CVE-2024-22034
- Published
- Oct 16, 2024
- Updated
- Oct 31, 2024
- Vendor
- NeuVector
- Product
- SUSE Linux Enterprise High Performance Computing
- Classifications
- T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 16, 2024CVE publishedPublication date reported by the CVE source.
- Oct 31, 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=? <1.9.0-150400.10.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