CVE-2022-23521

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 56% (99th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 56%
CISA-KEV: Not listedEPSS PROB: 56%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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 v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
82
EG Risk 82/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation56% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
56%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
56% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-23). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

January 17, 2023

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Oct 11, 2026
Patch available. Sources: github_commit, github.
Web page

Git: Multiple Vulnerabilities (GLSA 202312-15) — Gentoo security

https://security.gentoo.org/glsa/202312-15
GitHub advisoryMentions a patch (unverified)

gitattributes parsing integer overflow · Advisory · git/git · GitHub

https://github.com/git/git/security/advisories/GHSA-c738-c5qq-xg89
GitHub commit

commit 508386c6c585 (git/git)

Fix landed in git/git commit 508386c6c585 — awaiting tagged release

https://github.com/git/git/commit/508386c6c5857b4faa2c3e491f422c98cc69ae76

Vendor Advisories for CVE-2022-23521(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(13)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntugit-email (1:2.7.4-0ubuntu1.10+esm4) @ xenial2026-10-23ubuntu
ubuntugit-email (1:1.9.1-1ubuntu0.10+esm1) @ trusty2026-10-23ubuntu
ubuntugit-email (1:2.37.2-1ubuntu1.2) @ kinetic2026-10-23ubuntu
redhatredhat-virtualization-host-0:4.5.3-202304051438_8.62023-04-10redhat
redhatgit-0:1.8.3.1-24.el7_92023-02-28redhat
redhatgit-0:2.31.1-3.el9_02023-02-07redhat
redhatgit-0:2.31.1-3.el8_62023-02-07redhat
redhatgit-0:2.31.1-3.el9_12023-02-06redhat
redhatrh-git227-git-0:2.27.0-4.el72023-02-06redhat
redhatgit-0:2.27.0-3.el8_42023-02-06redhat
redhatgit-0:2.31.1-3.el8_72023-02-06redhat
redhatgit-0:2.18.4-2.el8_12023-02-06redhat
redhatgit-0:2.18.4-3.el8_22023-02-06redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(16 across 16 ecosystems)
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.31.0 up to 2.32.5-r0: fixed in 2.32.5-r0
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.31.0 up to 2.34.6-r0: fixed in 2.34.6-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.31.0 up to 2.36.4-r0: fixed in 2.36.4-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.31.0 up to 2.38.3-r0: fixed in 2.38.3-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.31.0 up to 2.39.1-r0: fixed in 2.39.1-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.31.0 up to 2.39.1-r0: fixed in 2.39.1-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.31.0 up to 2.39.1-r0: fixed in 2.39.1-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.31.0 up to 2.39.1-r0: fixed in 2.39.1-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.31.0 up to 2.39.1-r0: fixed in 2.39.1-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.31.0 up to 2.39.1-r0: fixed in 2.39.1-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.31.0 up to 2.39.1-r0: fixed in 2.39.1-r0
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
git1:2.20.1-2 ... 1:2.20.1-2+deb10u6 (7 versions)
  • every version up to 1:2.20.1-2+deb10u7: fixed in 1:2.20.1-2+deb10u7
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
git1:2.30.2-1
  • every version up to 1:2.30.2-1+deb11u1: fixed in 1:2.30.2-1+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • every version up to 1:2.39.1-0.1: fixed in 1:2.39.1-0.1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • every version up to 1:2.39.1-0.1: fixed in 1:2.39.1-0.1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • every version up to 1:2.39.1-0.1: fixed in 1:2.39.1-0.1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(13)

Data Freshness Timeline

(refreshed 21× in last 7d / 47× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 166 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 70 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 22:12 UTCEG score recompute
  2. 2026-10-23 22:12 UTCVendor advisory
  3. 2026-10-23 16:28 UTCEPSS rescoreEPSS 56% · 99th percentile
  4. 2026-10-22 22:56 UTCEG score recompute
  5. 2026-10-22 22:56 UTCVendor advisory
  6. 2026-10-22 16:30 UTCEPSS rescoreEPSS 56% · 99th percentile
  7. 2026-10-21 23:50 UTCEG score recompute
  8. 2026-10-21 23:50 UTCVendor advisory
  9. 2026-10-21 16:28 UTCEPSS rescoreEPSS 56% · 99th percentile
  10. 2026-10-21 00:45 UTCEG score recompute
  11. 2026-10-21 00:45 UTCVendor advisory
  12. 2026-10-20 16:29 UTCEPSS rescoreEPSS 56% · 99th percentile
  13. 2026-10-20 01:40 UTCEG score recompute
  14. 2026-10-20 01:40 UTCVendor advisory
  15. 2026-10-19 16:28 UTCEPSS rescoreEPSS 56% · 99th percentile
  16. 2026-10-19 00:38 UTCEG score recompute
  17. 2026-10-19 00:38 UTCVendor advisory
  18. 2026-10-18 08:42 UTCEG score recompute
  19. 2026-10-18 01:32 UTCEG score recompute
  20. 2026-10-18 01:32 UTCVendor advisory
  21. 2026-10-17 16:29 UTCEPSS rescoreEPSS 56% · 99th percentile
  22. 2026-10-17 02:21 UTCEG score recompute
  23. 2026-10-17 02:21 UTCVendor advisory
  24. 2026-10-16 16:34 UTCEPSS rescoreEPSS 56% · 99th percentile
  25. 2026-10-16 02:55 UTCEG score recompute
Show 71 more
  1. 2026-10-16 02:55 UTCVendor advisory
  2. 2026-10-15 16:28 UTCEPSS rescoreEPSS 56% · 99th percentile
  3. 2026-10-14 22:59 UTCEG score recompute
  4. 2026-10-14 22:59 UTCVendor advisory
  5. 2026-10-14 16:29 UTCEPSS rescoreEPSS 56% · 99th percentile
  6. 2026-10-13 18:37 UTCEG score recompute
  7. 2026-10-13 18:37 UTCVendor advisory
  8. 2026-10-13 16:29 UTCEPSS rescoreEPSS 56% · 99th percentile
  9. 2026-10-12 19:00 UTCVendor advisory
  10. 2026-10-12 18:59 UTCEG score recompute
  11. 2026-10-11 23:25 UTCEG score recompute
  12. 2026-10-11 13:44 UTCEPSS rescoreEPSS 56% · 99th percentile
  13. 2026-10-10 19:56 UTCEPSS rescoreEPSS 56% · 99th percentile
  14. 2026-10-09 20:04 UTCEPSS rescoreEPSS 56% · 99th percentile
  15. 2026-10-08 16:40 UTCEPSS rescoreEPSS 56% · 99th percentile
  16. 2026-10-07 23:45 UTCEPSS rescoreEPSS 56% · 99th percentile
  17. 2026-10-06 15:14 UTCEPSS rescoreEPSS 56% · 99th percentile
  18. 2026-10-04 23:19 UTCEPSS rescoreEPSS 56% · 99th percentile
  19. 2026-09-30 15:50 UTCEG score recompute
  20. 2026-09-30 15:00 UTCEPSS rescoreEPSS 56% · 99th percentile
  21. 2026-09-29 15:15 UTCEPSS rescoreEPSS 56% · 99th percentile
  22. 2026-09-24 14:00 UTCEPSS rescoreEPSS 56% · 99th percentile
  23. 2026-09-23 23:11 UTCOSV refresh
  24. 2026-09-23 13:45 UTCEPSS rescoreEPSS 56% · 99th percentile
  25. 2026-09-17 19:23 UTCEPSS rescoreEPSS 56% · 99th percentile
  26. 2026-09-16 14:05 UTCEPSS rescoreEPSS 56% · 99th percentile
  27. 2026-09-15 03:06 UTCEPSS rescoreEPSS 56% · 98th percentile
  28. 2026-09-13 16:43 UTCEPSS rescoreEPSS 56% · 98th percentile
  29. 2026-09-12 14:57 UTCEPSS rescoreEPSS 56% · 98th percentile
  30. 2026-09-11 09:33 UTCEPSS rescoreEPSS 56% · 98th percentile
  31. 2026-09-08 21:57 UTCEPSS rescoreEPSS 56% · 98th percentile
  32. 2026-09-06 13:45 UTCEPSS rescoreEPSS 56% · 98th percentile
  33. 2026-09-05 15:25 UTCEPSS rescoreEPSS 56% · 99th percentile
  34. 2026-09-04 17:29 UTCOSV refresh
  35. 2026-09-04 13:57 UTCEPSS rescoreEPSS 56% · 98th percentile
  36. 2026-09-02 14:09 UTCEPSS rescoreEPSS 56% · 98th percentile
  37. 2026-08-30 19:14 UTCEPSS rescoreEPSS 56% · 98th percentile
  38. 2026-08-30 01:19 UTCEPSS rescoreEPSS 56% · 99th percentile
  39. 2026-08-28 21:38 UTCEPSS rescoreEPSS 56% · 99th percentile
  40. 2026-08-26 14:43 UTCEPSS rescoreEPSS 56% · 98th percentile
  41. 2026-08-25 13:46 UTCEPSS rescoreEPSS 56% · 98th percentile
  42. 2026-08-24 14:13 UTCEPSS rescoreEPSS 56% · 98th percentile
  43. 2026-08-21 23:46 UTCEPSS rescoreEPSS 56% · 98th percentile
  44. 2026-08-20 22:52 UTCEPSS rescoreEPSS 56% · 98th percentile
  45. 2026-08-19 17:01 UTCEPSS rescoreEPSS 56% · 98th percentile
  46. 2026-08-18 13:45 UTCEPSS rescoreEPSS 56% · 98th percentile
  47. 2026-08-18 04:52 UTCOSV refresh
  48. 2026-08-17 13:44 UTCEPSS rescoreEPSS 56% · 98th percentile
  49. 2026-08-16 02:11 UTCEPSS rescoreEPSS 56% · 98th percentile
  50. 2026-08-15 01:27 UTCEPSS rescoreEPSS 56% · 98th percentile
  51. 2026-08-13 21:57 UTCEPSS rescoreEPSS 56% · 98th percentile
  52. 2026-08-12 13:48 UTCEPSS rescoreEPSS 56% · 98th percentile
  53. 2026-08-09 13:44 UTCEPSS rescoreEPSS 56% · 98th percentile
  54. 2026-08-07 16:24 UTCEPSS rescoreEPSS 56% · 98th percentile
  55. 2026-08-06 13:44 UTCEPSS rescoreEPSS 56% · 98th percentile
  56. 2026-08-04 10:34 UTCEPSS rescoreEPSS 56% · 98th percentile
  57. 2026-08-03 10:33 UTCEPSS rescoreEPSS 56% · 98th percentile
  58. 2026-08-02 23:57 UTCOSV refresh
  59. 2026-07-30 16:25 UTCEPSS rescoreEPSS 56% · 98th percentile
  60. 2026-07-30 01:28 UTCEPSS rescoreEPSS 56% · 98th percentile
  61. 2026-07-28 15:33 UTCEPSS rescoreEPSS 56% · 98th percentile
  62. 2026-07-26 14:52 UTCEPSS rescoreEPSS 56% · 98th percentile
  63. 2026-07-25 14:15 UTCEPSS rescoreEPSS 56% · 98th percentile
  64. 2026-07-24 14:15 UTCEPSS rescoreEPSS 56% · 98th percentile
  65. 2026-07-23 14:16 UTCEPSS rescoreEPSS 56% · 98th percentile
  66. 2026-07-23 02:08 UTCEG score recompute
  67. 2026-07-22 22:55 UTCEG score recompute
  68. 2026-07-22 14:06 UTCEPSS rescoreEPSS 56% · 98th percentile
  69. 2026-07-21 15:22 UTCEPSS rescoreEPSS 56% · 98th percentile
  70. 2026-07-20 17:05 UTCEPSS rescoreEPSS 56% · 98th percentile
  71. 2026-07-19 14:29 UTCEPSS rescoreEPSS 56% · 98th percentile

Frequently asked(5)

What is CVE-2022-23521?
CVE-2022-23521 is a critical-severity vulnerability; its CVE record was published on January 17, 2023. 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…
When was the CVE record for CVE-2022-23521 published?
The CVE record for CVE-2022-23521 was published on January 17, 2023. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2022-23521 actively exploited?
CVE-2022-23521 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 56% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-23521?
CVE-2022-23521 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2022-23521?
A fix for CVE-2022-23521 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-23521 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-23521

Explore →

Is Your Infrastructure Affected by CVE-2022-23521?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.