Koffei

CVE-2022-23521

🟠 Medium

git (scanner: git,git-man) · < 2.30.7; 2.31.x < 2.31.6; 2.32.x < 2.32.5; 2.33.x < 2.33.6; 2.34.x < 2.34.6; 2.35.x < 2.35.6; 2.36.x < 2.36.4; 2.37.x < 2.37.5; 2.38.x < 2.38.3; = 2.39.0

CVSS (Koffei note)
9.8
CVSS (v3.1, CVE List)
9.8
EPSS (2026-11-18)
56.334%
99.07th percentile

Exploitation

No (SSVC: none)

Timeline

  1. 17/01/2023CVE record published (CVE List)

Risk

9.8 Critical (v3.1) — AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, EPSS 56.334% (CWE-190 : Integer overflows in gitattributes parsing can give arbitrary heap read/write and potentially RCE via a crafted .gitattributes.)

Fix

Yes — 2.30.7 / 2.31.6 / 2.32.5 / 2.33.6 / 2.34.6 / 2.35.6 / 2.36.4 / 2.37.5 / 2.38.3 (per branch); 2.39.0 listed affected so fix is the next 2.39.x (not named in record) (advisory)

Official description

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.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE-190