CVE-2024-35197: medium-severity vulnerability in Byron gitoxide
gix refs and paths with reserved Windows device names access the devices
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.4epss 0.4%
gitoxide is a pure Rust implementation of Git. On Windows, fetching refs that clash with legacy device names reads from the devices, and checking out paths that clash with such names writes arbitrary data to the devices. This allows a repository, when cloned, to cause indefinite blocking or the production of arbitrary message that appear to have come from the application, and potentially other harmful effects under limited circumstances. If Windows is not used, or untrusted repositories are not cloned or otherwise used, then there is no impact. A minor degradation in availability may also be possible, such as with a very large file named `CON`, though the user could interrupt the application.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
Affected products
Byron · gitoxideRelated CVEs — Byron gitoxide
In the same product, most dangerous first.
CVE-2024-35186HIGHgix traversal outside working tree enables arbitrary code executionEPSS 0.8%CVE-2024-32884MEDIUMgix-transport indirect code execution via malicious usernameEPSS 0.5%CVE-2024-45405MEDIUMgix-path improperly resolves configuration path reported by GitEPSS 0.3%CVE-2024-45305LOWgix-path uses local config across repos when it is the highest scopeEPSS 0.2%CVE-2024-40644MEDIUMgitoxide's gix-path can use a fake program files locationEPSS 0.2%CVE-2024-43785LOWgitoxide-core does not neutralize special characters for terminalsEPSS 0.2%