CVE Tools
Track your stack

CVE-2024-50338

Carriage-return character in remote URL allows malicious repository to leak credentials in Git Credential Manager

No known exploitation. EPSS puts it in the 88th percentile. Fixed in 2.6.1.

CVSS 3.17.4HighEPSS percentile88th3.2% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix2.6.1Upgrade to this build
Check it yourself

OpenVAS · 2 checks

e.g. OID 1.3.6.1.4.1.25623.1.0.834577

Run the check

Published Updated Sources: CVE.org, NVD, GitHub, BDU

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • Git-ecosystem Git-credential-managerAffected: < 2.6.1Upgrade to: not statedStated by: CVE record
  • NuGet git-credential-managerAffected: < 2.6.1Upgrade to: 2.6.1Stated by: GitHub advisory
  • Microsoft Corp Microsoft Visual Studio 2022Affected: 17.6Upgrade to: not statedStated by: BDU
  • Microsoft Corp Microsoft Visual Studio 2017Affected: от 15.0 до 15.8 включительноUpgrade to: not statedStated by: BDU
  • Microsoft Corp Microsoft Visual Studio 2019Affected: от 16.0 до 16.10 включительноUpgrade to: not statedStated by: BDU

Versions as the sources state them. 1 more product has version data. Full version matrix after sign-in

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

Git Credential Manager (GCM) is a secure Git credential helper built on .NET that runs on Windows, macOS, and Linux. The Git credential protocol is text-based over standard input/output, and consists of a series of lines of key-value pairs in the format `key=value`. Git's documentation restricts the use of the NUL (`\0`) character and newlines to form part of the keys or values. When Git reads from standard input, it considers both LF and CRLF as newline characters for the credential protocol by virtue of calling `strbuf_getline` that calls to `strbuf_getdelim_strip_crlf`. Git also validates that a newline is not present in the value by checking for the presence of the line-feed character (LF, `\n`), and errors if this is the case. This captures both LF and CRLF-type newlines. Git Credential Manager uses the .NET standard library `StreamReader` class to read the standard input stream line-by-line and parse the `key=value` credential protocol format. The implementation of the `ReadLineAsync` method considers LF, CRLF, and CR as valid line endings. This is means that .NET considers a single CR as a valid newline character, whereas Git does not. This mismatch of newline treatment between Git and GCM means that an attacker can craft a malicious remote URL. When a user clones or otherwise interacts with a malicious repository that requires authentication, the attacker can capture credentials for another Git remote. The attack is also heightened when cloning from repositories with submodules when using the `--recursive` clone option as the user is not able to inspect the submodule remote URLs beforehand. This issue has been patched in version 2.6.1 and all users are advised to upgrade. Users unable to upgrade should only interact with trusted remote repositories, and not clone with `--recursive` to allow inspection of any submodule URLs before cloning those submodules.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS88th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

3.2% chance of exploitation activity in the next 30 days, which ranks it in the 88th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

6 events over 527 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Patch availablepublished, weakness classified, att&ck mapped, record updated

Affected products

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

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

Scored 7.4 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity NoneNo integrity impact
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 8 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Microsoft Corp, not every advisory.