CVE-2024-52005 | The sideband payload is passed unfiltered to the terminal in git

Git is a source code management tool. When cloning from a server (or fetching, or pushing), informational or error messages are transported from the remote Git process to the client via the so-called "sideband channel". These messages will be prefixed with "remote:" and printed directly to the standard error output. Typically, this standard error output is connected to a terminal that understands ANSI escape sequences, which Git did not protect against. Most modern terminals support control sequences that can be used by a malicious actor to hide and misrepresent information, or to mislead the user into executing untrusted scripts. As requested on the git-security mailing list, the patches are under discussion on the public mailing list. Users are advised to update as soon as possible. Users unable to upgrade should avoid recursive clones unless they are from trusted sources.

Published: 2025-01-15 Last update: 2025-12-18 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-52005 is rated Moderate Risk (51/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.38%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-52005

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-02-23 0.08% 0.38% +0.31%
2 2026-01-18 0.24% 0.08% -0.17%
3 2025-12-19 — 0.24% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-52005

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 4.0 HIGH
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network.
Attack complexity (AC:H)
Exploitation depends on constrained or hard-to-reproduce conditions.
Attack requirements (AT:N)
No additional preconditions are required beyond normal reachability.
Privileges required (PR:N)
No privileges are required.
User interaction (UI:A)
User interaction is required in an active way.
Vulnerable system confidentiality impact (VC:H)
High confidentiality impact on the vulnerable system.
Vulnerable system integrity impact (VI:H)
High integrity impact on the vulnerable system.
Vulnerable system availability impact (VA:H)
High availability impact on the vulnerable system.
Subsequent system confidentiality impact (SC:N)
No confidentiality impact on subsequent systems.
Subsequent system integrity impact (SI:N)
No integrity impact on subsequent systems.
Subsequent system availability impact (SA:N)
No availability impact on subsequent systems.
Exploit maturity (threat) (E:X)
Not defined: no reliable threat intelligence; scoring assumes the worst case (equivalent to Attacked).
Confidentiality requirement (CR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Integrity requirement (IR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Availability requirement (AR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Modified attack vector (MAV:X)
Not defined: scoring uses the Base Attack Vector (AV).
Modified attack complexity (MAC:X)
Not defined: scoring uses the Base Attack Complexity (AC).
Modified attack requirements (MAT:X)
Not defined: scoring uses the Base Attack Requirements (AT).
Modified privileges required (MPR:X)
Not defined: scoring uses the Base Privileges Required (PR).
Modified user interaction (MUI:X)
Not defined: scoring uses the Base User Interaction (UI).
Modified vulnerable system confidentiality impact (MVC:X)
Not defined: scoring uses the Base VC metric.
Modified vulnerable system integrity impact (MVI:X)
Not defined: scoring uses the Base VI metric.
Modified vulnerable system availability impact (MVA:X)
Not defined: scoring uses the Base VA metric.
Modified subsequent system confidentiality impact (MSC:X)
Not defined: scoring uses the Base SC metric.
Modified subsequent system integrity impact (MSI:X)
Not defined: scoring uses the Base SI metric.
Modified subsequent system availability impact (MSA:X)
Not defined: scoring uses the Base SA metric.
Safety (supplemental) (S:X)
Not evaluated.
Automatable (supplemental) (AU:X)
Not evaluated.
Recovery (supplemental) (R:X)
Not evaluated.
Value density (supplemental) (V:X)
Not evaluated.
Vulnerability response effort (supplemental) (RE:X)
Not evaluated.
Provider urgency (supplemental) (U:X)
Not evaluated.
 — — [email protected]
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]

Weakness enumeration for CVE-2024-52005

OS Trackers for CVE-2024-52005

vendor priority summary link
alpine — CVE-2024-52005: 1 source package rows (git); 82 state rows across 5 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 0, open 82. https://security.alpinelinux.org/vuln/CVE-2024-52005
debian unimportant CVE-2024-52005 unimportant priority: Debian including 1 source packages (git), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5. https://security-tracker.debian.org/tracker/CVE-2024-52005
redhat medium — https://access.redhat.com/security/cve/CVE-2024-52005
suse high CVE-2024-52005 severity important: SUSE including 52 source package names (git, git-2.43.5-3.el8_10, …), 397 product×package rows across 41 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Liberty Linux 8, … (41 product lines)): Known Not Affected 303, Will Not Fix 64, Fixed 30. https://www.suse.com/security/cve/CVE-2024-52005/
ubuntu medium CVE-2024-52005 medium priority: Ubuntu including 1 source packages (git), 9 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream, xenial): deferred 6, ignored 2, needs-triage 1. https://ubuntu.com/security/CVE-2024-52005

Affected software / configurations for CVE-2024-52005

Vendor Product Version Raw CPE
git git <= 2.40.4 cpe:2.3:a:git:git:*:*:*:*:*:*:*:*
git git >= 2.41.0, <= 2.41.3 cpe:2.3:a:git:git:*:*:*:*:*:*:*:*
git git >= 2.42.0, <= 2.42.4 cpe:2.3:a:git:git:*:*:*:*:*:*:*:*
git git >= 2.43.0, <= 2.43.6 cpe:2.3:a:git:git:*:*:*:*:*:*:*:*
git git >= 2.44.0, <= 2.44.3 cpe:2.3:a:git:git:*:*:*:*:*:*:*:*
git git >= 2.45.0, <= 2.45.3 cpe:2.3:a:git:git:*:*:*:*:*:*:*:*
git git >= 2.46.0, <= 2.46.3 cpe:2.3:a:git:git:*:*:*:*:*:*:*:*
git git >= 2.47.0, <= 2.47.1 cpe:2.3:a:git:git:*:*:*:*:*:*:*:*
git git >= 2.48.0, <= 2.48.1 cpe:2.3:a:git:git:*:*:*:*:*:*:*:*

References for CVE-2024-52005

cvelogic Threat Intelligence