MediumCVE-2024-50349

    Git does not sanitize URLs when asking for credentials interactively (CVE-2024-50349)

    Published Sources: CVE.org, Msrc Update Guide, OSV

    What is affected, what to do

    Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. When Git asks for credentials via a terminal prompt (i.e. without using any credential helper), it prints out the host name for which the user is expected to provide a username and/or a password.

    Update git to version 2.41.3.

    Affected
    • Git gte 2.41.0, <= 2.41.2..*
    • Git lte *..2.40.3
    • Git eq 2.48.0..2.48.0

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    4.7

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    4.7

    CVSS v3

    Severity Medium on the scale from 0 to 10.

    Source: CVE.org, Msrc Update Guide, OSV

    0.7 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 51.0

    Show all metrics
    Severity
    Medium
    Priority score

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    51.84
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    4.7
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    4.7
    CVSS v4

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    2.1
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.7 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    51.0
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-116, CWE-147, CWE-150

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. When Git asks for credentials via a terminal prompt (i.e. without using any credential helper), it prints out the host name for which the user is expected to provide a username and/or a password. At this stage, any URL-encoded parts have been decoded already, and are printed verbatim. This allows attackers to craft URLs that contain ANSI escape sequences that the terminal interpret to confuse users e.g. into providing passwords for trusted Git hosting sites when in fact they are then sent to untrusted sites that are under the attacker's control. This issue has been patch via commits `7725b81` and `c903985` which are included in release versions v2.48.1, v2.47.2, v2.46.3, v2.45.3, v2.44.3, v2.43.6, v2.42.4, v2.41.3, and v2.40.4. Users are advised to upgrade. Users unable to upgrade should avoid cloning from untrusted URLs, especially recursive clones.

    Source: NVD (NIST), cvelistv5, CVE.org (MITRE), Microsoft Security Update Guide, OSV (Open Source Vulnerabilities)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    VendorProductAffected versionsFixed in
    gitgit
    • ≥ 2.41.0, <= 2.41.2
    • 2.48.0
    • ≤ 2.40.3
    • 2.41.0 – < 2.41.3
    • 2.42.0 – < 2.42.4
    • 2.43.0 – < 2.43.6
    • < 2.44.3
    • < 2.45.3
    • < 2.46.3
    • 2.47.0 – < 2.47.2
    • 2.48.0
    • < 2.40.4
    • —
    • —
    • —
    • 2.41.3
    • 2.42.4
    • 2.43.6
    • 2.44.3
    • 2.45.3
    • 2.46.3
    • 2.47.2
    • —
    • 2.40.4
    Distribution and container packages (8)

    Downstream packages (e.g. Bitnami, Debian, Ubuntu, Red Hat). Versions refer to the distribution, not the vendor.

    Distribution and container packages
    VendorProductAffected versionsFixed in
    bitnamigit
    • 2.41.0
    • 2.42.0
    • 2.43.0
    • 2.44.0
    • 2.45.0
    • 2.46.0
    • 2.47.0
    • 2.48.0
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —

    Affected operating systems

    Affected operating systems
    FamilyVendorProductVersion
    Linuxdebiandebian_linux11.0

    Weakness classes (CWE)

    • CWE-116Improper Encoding or Escaping of Output

      Class

      The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.

      Entry at MITRE CWE-116

    • CWE-147Improper Neutralization of Input Terminators

      Variant

      The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as input terminators when they are sent to a downstream component.

      Entry at MITRE CWE-147

    • CWE-150Improper Neutralization of Escape, Meta, or Control Sequences

      Variant

      The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as escape, meta, or control character sequences when they are sent to a downstream component.

      Entry at MITRE CWE-150

    References & sources

    • github.comgit/git/security/advisories/GHSA-hmg8-h7qf-7cxrx_refsource_CONFIRM, Patch, Vendor advisory
    • github.comgit/git/commit/7725b8100ffbbff2750ee4d61a0fcc1f53a086e8x_refsource_MISC, Patch
    • github.comgit/git/commit/c903985bf7e772e2d08275c1a95c8a55ab011577x_refsource_MISC, Patch
    • lists.debian.orgdebian-lts-announce/2025/01/msg00025.htmlMailing list, Third-party advisory
    • NVD (NIST)vuln/detail/CVE-2024-50349web