Skip to content
Noroxi
CVE-2024-52005· NVD / CVE Program· CNA GitHub_M

The sideband payload is passed unfiltered to the terminal in git

Noroxi assessment

Priority: Monitor (action score 30/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.51% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. Special conditions such as timing or configuration are required.
  • Fixed version: git (AlmaLinux:10) 2.47.1-2.el10_0; git-all (AlmaLinux:10) 2.47.1-2.el10_0; git-core (AlmaLinux:10) 2.47.1-2.el10_0.

Low priority for now. Upgrade to git (AlmaLinux:10) 2.47.1-2.el10_0; git-all (AlmaLinux:10) 2.47.1-2.el10_0; git-core (AlmaLinux:10) 2.47.1-2.el10_0 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 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.

HighCVSS 7.5 · v4.0—Proof of concept Fix available
Published
Jan 15, 2025
Updated
Jun 17, 2026
EPSS
0.5% · 42th percentile

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
7.5
NVD has not scored this yet; the score shown is the CNA’s.

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

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
  • Proof of concept exists, no weaponized module
  • A fix has been released

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

Follow CVE-2024-52005

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 instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack 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 (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

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for git records

Running WordPress? Scan your site free with WP Lens

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
gitgit

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • git gitup to 2.40.4 inclusive
  • git git2.41.0 and later · up to 2.41.3 inclusive
  • git git2.42.0 and later · up to 2.42.4 inclusive
  • git git2.43.0 and later · up to 2.43.6 inclusive
  • git git2.44.0 and later · up to 2.44.3 inclusive
  • git git2.45.0 and later · up to 2.45.3 inclusive
  • git git2.46.0 and later · up to 2.46.3 inclusive
  • git git2.47.0 and later · up to 2.47.1 inclusive
  • git git2.48.0 and later · up to 2.48.1 inclusive

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.48.0, <= 2.48.1, >= 2.47.0, <= 2.47.1, >= 2.46.0, <= 2.46.3, >= 2.45.0, <= 2.45.3, >= 2.44.0, <= 2.44.3, >= 2.43.0, <= 2.43.6, >= 2.42.0, <= 2.42.4, >= 2.41.0, <= 2.41.3, <= 2.40.4affected

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10gitbefore 2.47.1-2.el10_02.47.1-2.el10_0
AlmaLinux:10git-allbefore 2.47.1-2.el10_02.47.1-2.el10_0
AlmaLinux:10git-corebefore 2.47.1-2.el10_02.47.1-2.el10_0
AlmaLinux:10git-core-docbefore 2.47.1-2.el10_02.47.1-2.el10_0
AlmaLinux:10git-credential-libsecretbefore 2.47.1-2.el10_02.47.1-2.el10_0
AlmaLinux:10git-daemonbefore 2.47.1-2.el10_02.47.1-2.el10_0
AlmaLinux:10git-emailbefore 2.47.1-2.el10_02.47.1-2.el10_0
AlmaLinux:10git-guibefore 2.47.1-2.el10_02.47.1-2.el10_0
AlmaLinux:10git-instawebbefore 2.47.1-2.el10_02.47.1-2.el10_0
AlmaLinux:10git-subtreebefore 2.47.1-2.el10_02.47.1-2.el10_0
AlmaLinux:10git-svnbefore 2.47.1-2.el10_02.47.1-2.el10_0
AlmaLinux:10gitkbefore 2.47.1-2.el10_02.47.1-2.el10_0
AlmaLinux:10gitwebbefore 2.47.1-2.el10_02.47.1-2.el10_0
AlmaLinux:10perl-Gitbefore 2.47.1-2.el10_02.47.1-2.el10_0
AlmaLinux:10perl-Git-SVNbefore 2.47.1-2.el10_02.47.1-2.el10_0
AlmaLinux:8gitbefore 2.43.5-3.el8_102.43.5-3.el8_10
AlmaLinux:8git-allbefore 2.43.5-3.el8_102.43.5-3.el8_10
AlmaLinux:8git-corebefore 2.43.5-3.el8_102.43.5-3.el8_10
AlmaLinux:8git-core-docbefore 2.43.5-3.el8_102.43.5-3.el8_10
AlmaLinux:8git-credential-libsecretbefore 2.43.5-3.el8_102.43.5-3.el8_10
AlmaLinux:8git-daemonbefore 2.43.5-3.el8_102.43.5-3.el8_10
AlmaLinux:8git-emailbefore 2.43.5-3.el8_102.43.5-3.el8_10
AlmaLinux:8git-guibefore 2.43.5-3.el8_102.43.5-3.el8_10
AlmaLinux:8git-instawebbefore 2.43.5-3.el8_102.43.5-3.el8_10

+96

Same product

git: all records

Other highest-scoring records for the same primary product.

  • CVE-2024-32002Git's recursive clones on case-insensitive filesystems that support symlinks are susceptible to Remote Code Execution
    45Plan
  • CVE-2022-25648The package git before 1.11.0 are vulnerable to Command Injection via git argument injection.
    40Plan
  • CVE-2025-48385Git alllows arbitrary file writes via bundle-uri parameter injection
    34Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2024-50349Jan 14, 2025 · Git does not sanitize URLs when asking for credentials interactively
    8Monitor
  • ← EarlierCVE-2024-52006Jan 14, 2025 · Newline confusion in credential helpers can lead to credential exfiltration in git
    8Monitor
  • Later →CVE-2025-48386Jul 8, 2025 · Git allows a buffer overflow in 'wincred' credential helper
    25Monitor

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.47.1-2.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:git-all2.47.1-2.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:git-core2.47.1-2.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:git-core-doc2.47.1-2.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:git-credential-libsecret2.47.1-2.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:git-daemon2.47.1-2.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:git-email2.47.1-2.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:git-gui2.47.1-2.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:git-instaweb2.47.1-2.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:git-subtree2.47.1-2.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:git-svn2.47.1-2.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:gitk2.47.1-2.el9_6 · AlmaLinux:9Package registry (OSV)
red hat:git0:2.47.1-2.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-all0:2.47.1-2.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-core0:2.47.1-2.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-core-debuginfo0:2.47.1-2.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-core-doc0:2.47.1-2.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-credential-libsecret0:2.47.1-2.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-credential-libsecret-debuginfo0:2.47.1-2.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-daemon0:2.47.1-2.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-daemon-debuginfo0:2.47.1-2.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-debuginfo0:2.47.1-2.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-debugsource0:2.47.1-2.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-email0:2.47.1-2.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
rocky linux:git0:2.47.1-2.el9_6 · Rocky Linux:9Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02025-12-29

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.

  1. Published
  2. First PoC+347 d
  3. TodayOct 18, 2026+641 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

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

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2024-503491 days apartGit does not sanitize URLs when asking for credentials interactively
    8Monitor
  • CVE-2024-520061 days apartNewline confusion in credential helpers can lead to credential exfiltration in git
    8Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
A
Scope
X

Weakness class (CWE)

CWE-116 · Improper Encoding or Escaping of Output

CVSS vector

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

nvd-secondary

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

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (1 more)

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

All records