CVE-2022-23521: gitattributes parsing integer overflow in git
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.
- BDU:2023-00499
- ALSA-2023:0610
- ALSA-2023:0611
- DLA-3282-1
- DSA-5332-1
- openSUSE-SU-2024:12625-1
- RHSA-2023:0596
- RHSA-2023:0597
- RHSA-2023:0599
- RHSA-2023:0609
- RHSA-2023:0610
- RHSA-2023:0611
- RHSA-2023:0627
- RHSA-2023:0628
- RHSA-2023:0978
- RHSA-2023:1677
- RLSA-2023:0610
- RLSA-2023:0611
- SUSE-SU-2023:0108-1
- SUSE-SU-2023:0109-1
- Published
- Jan 17, 2023
- Updated
- Jun 17, 2026
- EPSS
- 56.3% · 99th percentile
- CWE
- CWE-190
Report tools
Action score
56
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| git-scm | git | cpe:2.3:a:git-scm:git |
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
Affected versions · NVD (10)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- git-scm gitup to 2.30.6 inclusive
- git-scm git2.31.0 and later · up to 2.31.5 inclusive
- git-scm git2.32.0 and later · up to 2.32.4 inclusive
- git-scm git2.33.0 and later · up to 2.33.5 inclusive
- git-scm git2.34.0 and later · up to 2.34.5 inclusive
- git-scm git2.35.0 and later · up to 2.35.5 inclusive
- git-scm git2.36.0 and later · up to 2.36.3 inclusive
- git-scm git2.37.0 and later · up to 2.37.4 inclusive
- git-scm git2.38.0 and later · up to 2.38.2 inclusive
- git-scm git2.39.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | git | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | git-all | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | git-core | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | git-core-doc | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | git-credential-libsecret | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | git-daemon | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | git-email | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | git-gui | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | git-instaweb | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | git-subtree | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | git-svn | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | gitk | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | gitweb | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | perl-Git | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | perl-Git-SVN | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:9 | git | before 2.31.1-3.el9_1 | 2.31.1-3.el9_1 |
| AlmaLinux:9 | git-all | before 2.31.1-3.el9_1 | 2.31.1-3.el9_1 |
| AlmaLinux:9 | git-core | before 2.31.1-3.el9_1 | 2.31.1-3.el9_1 |
| AlmaLinux:9 | git-core-doc | before 2.31.1-3.el9_1 | 2.31.1-3.el9_1 |
| AlmaLinux:9 | git-credential-libsecret | before 2.31.1-3.el9_1 | 2.31.1-3.el9_1 |
| AlmaLinux:9 | git-daemon | before 2.31.1-3.el9_1 | 2.31.1-3.el9_1 |
| AlmaLinux:9 | git-email | before 2.31.1-3.el9_1 | 2.31.1-3.el9_1 |
| AlmaLinux:9 | git-gui | before 2.31.1-3.el9_1 | 2.31.1-3.el9_1 |
| AlmaLinux:9 | git-instaweb | before 2.31.1-3.el9_1 | 2.31.1-3.el9_1 |
+96
Same product
git-scm: all recordsOther 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 quotingKEV63This week
- CVE-2021-21300malicious repositories can execute remote code while cloning60This 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-windows33Monitor
- Later →CVE-2022-41903Jan 17, 2023 · Integer overflow in `git archive`, `git log --format` leading to RCE in git52Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:git | 2.31.1-3.el8_7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:git-all | 2.31.1-3.el8_7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:git-core | 2.31.1-3.el8_7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:git-core-doc | 2.31.1-3.el8_7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:git-credential-libsecret | 2.31.1-3.el8_7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:git-daemon | 2.31.1-3.el8_7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:git-email | 2.31.1-3.el8_7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:git-gui | 2.31.1-3.el8_7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:git-instaweb | 2.31.1-3.el8_7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:git-subtree | 2.31.1-3.el8_7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:git-svn | 2.31.1-3.el8_7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:gitk | 2.31.1-3.el8_7 · AlmaLinux:8 | Package registry (OSV) |
| alpine:git | 2.32.5-r0 · Alpine:v3.14 | Package registry (OSV) |
| debian:git | 1:2.39.1-0.1 · Debian:12 | Package registry (OSV) |
| opensuse:git | 2.26.2-150000.44.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| red hat:git | 0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstream | Package registry (OSV) |
| red hat:git-all | 0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstream | Package registry (OSV) |
| red hat:git-core | 0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstream | Package registry (OSV) |
| red hat:git-core-debuginfo | 0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstream | Package registry (OSV) |
| red hat:git-core-doc | 0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstream | Package registry (OSV) |
| red hat:git-credential-libsecret | 0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstream | Package registry (OSV) |
| red hat:git-credential-libsecret-debuginfo | 0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstream | Package registry (OSV) |
| red hat:git-daemon | 0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstream | Package registry (OSV) |
| red hat:git-daemon-debuginfo | 0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstream | Package registry (OSV) |
| red hat:git-debuginfo | 0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstream | Package registry (OSV) |
| red hat:git-debugsource | 0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstream | Package registry (OSV) |
| red hat:git-email | 0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstream | Package registry (OSV) |
| rocky linux:git | 0:2.31.1-3.el8_7 · Rocky Linux:8 | Package registry (OSV) |
| suse:git | 2.26.2-150000.44.1 · SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | Package 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.
- TR-23-0100 · Feb 21, 2023(OpenShift Güvenlik Güncellemesi)
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
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS 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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.