CVE-2022-23521

What it is

Git is distributed revision control system. gitattributes are a mechanism to allow defining attributes for paths. These attributes can be defined by adding a `.gitattributes` file to the repository, which contains a set of file patterns and the attributes that should be set for paths matching this pattern. When parsing gitattributes, multiple integer overflows can occur when there is a huge number of path patterns, a huge number of attributes for a single pattern, or when the declared attribute names are huge. These overflows can be triggered via a crafted `.gitattributes` file that may be part of the commit history. Git silently splits lines longer than 2KB when parsing gitattributes from a file, but not when parsing them from the index. Consequentially, the failure mode depends on whether the file exists in the working tree, the index or both. This integer overflow can result in arbitrary heap reads and writes, which may result in remote code execution. The problem has been patched in the versions published on 2023-01-17, going back to v2.30.7. Users are advised to upgrade. There are no known workarounds for this issue.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.

Exploit odds

56.3% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2022-01-19 21:23 UTC ReservedThe CVE id was reserved by its CNA
2. 2023-01-17 23:15 UTC PublishedDisclosed publicly on CVE.org and NVD
3. 2026-06-17 04:30 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 56.3% in the next 30 days (EPSS).
• Severity: 9.8 CRITICAL (CVSS).
• Fix: a patch or advisory is linked.
• It meets the bar for Drop everything: critical, and exploited or very likely to be.

Details

Published

2023-01-17 23:15 UTC

Last modified

2026-06-17 04:30 UTC

Exploit probability

56.3% · EPSS, next 30 days

Weakness

CWE-190 · Integer overflow

Record status

Modified

Affected

• git-scm Git ≤ 2.30.6
• git-scm Git ≤ 2.31.5
• git-scm Git ≤ 2.32.4
• git-scm Git ≤ 2.33.5
• git-scm Git ≤ 2.34.5
• git-scm Git ≤ 2.35.5
• git-scm Git ≤ 2.36.3
• git-scm Git ≤ 2.37.4

Attack profile CVSS 3.1 · 9.8

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2022-23521.md and follow it. Check whether this project is affected by CVE-2022-23521. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge