Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2022-23521: gitattributes parsing integer overflow in git

CriticalCVSS 9.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Plan (action score 56/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 56.3% (FIRST EPSS); higher than 99% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: git (AlmaLinux:8) 2.31.1-3.el8_7; git-all (AlmaLinux:8) 2.31.1-3.el8_7; git-core (AlmaLinux:8) 2.31.1-3.el8_7.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Add it to your regular patch cycle. Upgrade to git (AlmaLinux:8) 2.31.1-3.el8_7; git-all (AlmaLinux:8) 2.31.1-3.el8_7; git-core (AlmaLinux:8) 2.31.1-3.el8_7 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Jan 17, 2023
Updated
Jun 17, 2026
EPSS
56.3% · 99th percentile

Report tools

JSON

Action score

56

Plan

Add it to your regular patch cycle.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
17 / 30 · 56.3%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
9.8
CNA · GitHub_M
9.8
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-23521

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
git-scmgit

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • git git

    • < 2.30.7, >= 2.31.0, < 2.31.6, >= 2.32.0, < 2.32.5, >= 2.33.0, < 2.33.6, >= 2.34.0, < 2.34.6, >= 2.35.0, < 2.35.6, >= 2.36.0, < 2.36.4, >= 2.37.0, < 2.37.5, >= 2.38.0, < 2.38.3, = 2.39.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8gitbefore 2.31.1-3.el8_72.31.1-3.el8_7
AlmaLinux:8git-allbefore 2.31.1-3.el8_72.31.1-3.el8_7
AlmaLinux:8git-corebefore 2.31.1-3.el8_72.31.1-3.el8_7
AlmaLinux:8git-core-docbefore 2.31.1-3.el8_72.31.1-3.el8_7
AlmaLinux:8git-credential-libsecretbefore 2.31.1-3.el8_72.31.1-3.el8_7
AlmaLinux:8git-daemonbefore 2.31.1-3.el8_72.31.1-3.el8_7
AlmaLinux:8git-emailbefore 2.31.1-3.el8_72.31.1-3.el8_7
AlmaLinux:8git-guibefore 2.31.1-3.el8_72.31.1-3.el8_7
AlmaLinux:8git-instawebbefore 2.31.1-3.el8_72.31.1-3.el8_7
AlmaLinux:8git-subtreebefore 2.31.1-3.el8_72.31.1-3.el8_7
AlmaLinux:8git-svnbefore 2.31.1-3.el8_72.31.1-3.el8_7
AlmaLinux:8gitkbefore 2.31.1-3.el8_72.31.1-3.el8_7
AlmaLinux:8gitwebbefore 2.31.1-3.el8_72.31.1-3.el8_7
AlmaLinux:8perl-Gitbefore 2.31.1-3.el8_72.31.1-3.el8_7
AlmaLinux:8perl-Git-SVNbefore 2.31.1-3.el8_72.31.1-3.el8_7
AlmaLinux:9gitbefore 2.31.1-3.el9_12.31.1-3.el9_1
AlmaLinux:9git-allbefore 2.31.1-3.el9_12.31.1-3.el9_1
AlmaLinux:9git-corebefore 2.31.1-3.el9_12.31.1-3.el9_1
AlmaLinux:9git-core-docbefore 2.31.1-3.el9_12.31.1-3.el9_1
AlmaLinux:9git-credential-libsecretbefore 2.31.1-3.el9_12.31.1-3.el9_1
AlmaLinux:9git-daemonbefore 2.31.1-3.el9_12.31.1-3.el9_1
AlmaLinux:9git-emailbefore 2.31.1-3.el9_12.31.1-3.el9_1
AlmaLinux:9git-guibefore 2.31.1-3.el9_12.31.1-3.el9_1
AlmaLinux:9git-instawebbefore 2.31.1-3.el9_12.31.1-3.el9_1

+96

Other highest-scoring records for the same primary product.

  • CVE-2018-17456Git before 2.14.5, 2.15.x before 2.15.3, 2.16.x before 2.16.5, 2.17.x before 2.17.2, 2.18.x before 2.18.1, and 2.19.x before 2.19.1 allows…
    68This week
  • CVE-2025-48384Git allows arbitrary code execution through broken config quotingKEV
    63This week
  • CVE-2021-21300malicious repositories can execute remote code while cloning
    60This week

Published before and after this one in the same product

  • ← EarlierCVE-2022-39260Oct 19, 2022 · Git vulnerable to Remote Code Execution via Heap overflow in `git shell`
    36Monitor
  • ← EarlierCVE-2022-41953Jan 17, 2023 · Git clone remote code execution vulnerability in git-for-windows
    33Monitor
  • Later →CVE-2022-41903Jan 17, 2023 · Integer overflow in `git archive`, `git log --format` leading to RCE in git
    52Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:git2.31.1-3.el8_7 · AlmaLinux:8Package registry (OSV)
almalinux:git-all2.31.1-3.el8_7 · AlmaLinux:8Package registry (OSV)
almalinux:git-core2.31.1-3.el8_7 · AlmaLinux:8Package registry (OSV)
almalinux:git-core-doc2.31.1-3.el8_7 · AlmaLinux:8Package registry (OSV)
almalinux:git-credential-libsecret2.31.1-3.el8_7 · AlmaLinux:8Package registry (OSV)
almalinux:git-daemon2.31.1-3.el8_7 · AlmaLinux:8Package registry (OSV)
almalinux:git-email2.31.1-3.el8_7 · AlmaLinux:8Package registry (OSV)
almalinux:git-gui2.31.1-3.el8_7 · AlmaLinux:8Package registry (OSV)
almalinux:git-instaweb2.31.1-3.el8_7 · AlmaLinux:8Package registry (OSV)
almalinux:git-subtree2.31.1-3.el8_7 · AlmaLinux:8Package registry (OSV)
almalinux:git-svn2.31.1-3.el8_7 · AlmaLinux:8Package registry (OSV)
almalinux:gitk2.31.1-3.el8_7 · AlmaLinux:8Package registry (OSV)
alpine:git2.32.5-r0 · Alpine:v3.14Package registry (OSV)
debian:git1:2.39.1-0.1 · Debian:12Package registry (OSV)
opensuse:git2.26.2-150000.44.1 · openSUSE:Leap 15.4Package registry (OSV)
red hat:git0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstreamPackage registry (OSV)
red hat:git-all0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstreamPackage registry (OSV)
red hat:git-core0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstreamPackage registry (OSV)
red hat:git-core-debuginfo0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstreamPackage registry (OSV)
red hat:git-core-doc0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstreamPackage registry (OSV)
red hat:git-credential-libsecret0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstreamPackage registry (OSV)
red hat:git-credential-libsecret-debuginfo0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstreamPackage registry (OSV)
red hat:git-daemon0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstreamPackage registry (OSV)
red hat:git-daemon-debuginfo0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstreamPackage registry (OSV)
red hat:git-debuginfo0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstreamPackage registry (OSV)
red hat:git-debugsource0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstreamPackage registry (OSV)
red hat:git-email0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstreamPackage registry (OSV)
rocky linux:git0:2.31.1-3.el8_7 · Rocky Linux:8Package registry (OSV)
suse:git2.26.2-150000.44.1 · SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSSPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records