git: Process Control
CVE-2024-32004 is a high-severity process control vulnerability in git, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists versions 2.43.4, 2.42.2, 2.40.2 as the first without the flaw, so updating git to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.35% chance of exploitation within 30 days, higher than 72% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update git to 2.43.4 or 2.42.2 or 2.40.2 or 2.39.4, whichever matches your release line, or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Git | git | = 2.45.0; = 2.44.0; >= 2.43.0, < 2.43.4; >= 2.42.0, < 2.42.2; = 2.41.0; >= 2.40.0, < 2.40.2; < 2.39.4; 2.45.0; and 6 more ranges | 2.43.4, 2.42.2, 2.40.2, 2.39.4 |
| Fedora Project | Fedora | 40 | Not stated |
| Debian | Debian Linux | 10.0; 11.0 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.1 | High | CNA (github.com) |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, an attacker can prepare a local repository in such a way that, when cloned, will execute arbitrary code during the operation. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid cloning repositories from untrusted sources.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Process Control
Executing commands or loading libraries from an untrusted source or in an untrusted environment can cause an application to execute malicious commands (and payloads) on behalf of an attacker.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Patches and release notes
Third-party and government advisories
- openwall.com/lists/oss-security/2024/05/14/2Mailing List, Third Party Advisory
Other references
- git-scm.com/docs/git-cloneTechnical Description
Other vulnerabilities in git
- 7.5 High severity
- 8.6 High severity
- 8.0 High severity
Git Link Following Exploited
- 8.8 High severity
- 7.5 High severity
- 7.8 High severity
Recent Process Control vulnerabilities
- 8.4 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.