CVE-2024-22034
Crafted projects can overwrite special files in the .osc config directory
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.9.0-150400.10.6.1, 0.183.0-15.18.1, 1.9.0-1.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Attackers could put the special files in .osc into the actual package sources (e.g. _apiurl). This allows the attacker to change the configuration of osc for the victim
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- osc
fixed in 1.9.0-150400.10.6.1
- osc
fixed in 1.9.0-150400.10.6.1
- osc
fixed in 1.9.0-150400.10.6.1
- osc
fixed in 1.9.0-150400.10.6.1
- osc
fixed in 1.9.0-150400.10.6.1
- osc
fixed in 1.9.0-150400.10.6.1
- osc
fixed in 1.9.0-150400.10.6.1
- osc
fixed in 1.9.0-150400.10.6.1
- osc
fixed in 1.9.0-150400.10.6.1
- osc
fixed in 1.9.0-150400.10.6.1
- osc
fixed in 0.183.0-15.18.1
- osc
fixed in 0.183.0-15.18.1
- osc
fixed in 0.183.0-15.18.1
- osc
fixed in 1.9.0-150400.10.6.1
- osc
fixed in 1.9.0-150400.10.6.1
- osc
fixed in 1.9.0-1.1