Security readout for executives and security teams
Plain-English summary
Git versions before 2.30.1 could mishandle repository paths containing newline characters. A crafted repository URL could make Git send unexpected requests using another protocol. This matters most where automation, CI, developer tools, or services accept repository URLs from less-trusted users.
Executive priority
Treat this as a targeted remediation item, not an emergency based on current evidence. Prioritize internet-facing or multi-tenant automation that accepts repository URLs, then fold remaining Git upgrades into standard maintenance.
Technical view
The issue is in git_connect_git in connect.c. Git did not properly reject newline characters in repository paths, enabling unexpected cross-protocol requests. Public sources identify the fix in Git 2.30.1 and related upstream commit history. No CVSS, CWE, or product-specific package matrix is provided in the bundle.
Likely exposure
Exposure is most likely on systems running Git before 2.30.1, especially CI/CD, code hosting integrations, scanners, or build services that fetch repositories from externally supplied URLs.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. The described abuse depends on a crafted repository path being processed by a vulnerable Git client.
Researcher notes
Evidence is limited to the CVE record, upstream Git fix references, and a Debian LTS advisory. The bundle does not provide CVSS, CWE classification, proof of active exploitation, or a comprehensive affected-package list.
Mitigation direction
- Upgrade Git to 2.30.1 or a vendor-maintained fixed package.
- Check operating system vendor advisories for backported Git security fixes.
- Prioritize systems that clone or fetch repositories from user-controlled URLs.
- Reduce acceptance of untrusted repository URLs where feasible.
Validation and detection
- Inventory Git versions on developer workstations, build agents, and automation hosts.
- Confirm vulnerable hosts are not running Git before 2.30.1 without vendor backports.
- Review CI and service logs for repository URLs containing encoded control characters.
- Verify vendor package changelogs include the CVE-2021-40330 fix.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2021-40330 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/git/git/commit/a02ea577174ab8ed18f847cf1693f213e0b9c473CVE reference
- https://github.com/git/git/compare/v2.30.0...v2.30.1CVE reference
- [debian-lts-announce] 20221010 [SECURITY] [DLA 3145-1] git security updateCVE reference · mailing-list
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.