Security readout for executives and security teams
Plain-English summary
Older Git installations could run unintended commands when a developer enters a malicious repository and their shell prompt displays the current branch. The issue is tied to Git's optional git-prompt.sh helper before Git 1.9.3. It is mainly a developer workstation and build-image risk, not a remotely reachable server bug.
Executive priority
Treat as a targeted developer-environment risk. Prioritize cleanup where employees handle untrusted repositories or where build systems use old images. The age of the issue lowers urgency if asset inventory confirms modern Git everywhere.
Technical view
contrib/completion/git-prompt.sh in Git before 1.9.3 failed to sanitize branch names before placing them in PS1. A malicious repository branch name could influence shell prompt evaluation and lead to code execution when the prompt is rendered. The Git commit reference indicates the upstream fix; Red Hat also issued an advisory.
Likely exposure
Exposure is most likely on legacy developer workstations, CI images, jump hosts, or admin shells using Git before 1.9.3 and sourcing git-prompt.sh in PS1. Modern Git packages are unlikely to be affected unless old vendor builds remain in use.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation evidence. Public references include a repository and the upstream fixing commit, so proof-of-concept awareness may exist, but active exploitation should not be assumed from these sources alone.
Researcher notes
The CVE record lacks CVSS, CWE, and structured affected-product data beyond the description. Analysis should stay anchored to Git before 1.9.3 and git-prompt.sh PS1 handling. Do not expand scope to other shells, prompts, or Git integrations without separate evidence.
Mitigation direction
- Upgrade Git to 1.9.3 or a vendor-supported fixed package.
- Apply relevant vendor advisories, including Red Hat guidance where applicable.
- Remove or disable vulnerable git-prompt.sh usage on legacy systems until patched.
- Retire old developer and CI images that ship affected Git versions.
- Check vendor documentation for distribution-specific backports.
Validation and detection
- Inventory Git versions on developer workstations, CI runners, and admin hosts.
- Identify shell profiles that source contrib/completion/git-prompt.sh.
- Confirm deployed packages include the upstream sanitization fix or vendor backport.
- Review golden images and containers for Git versions before 1.9.3.
- Record exceptions where Git cannot be updated immediately.
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.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2014-9938 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/njhartwell/pw3nageCVE reference · x_refsource_MISC
- https://github.com/git/git/commit/8976500cbbb13270398d3b3e07a17b8cc7bff43fCVE reference · x_refsource_CONFIRM
- RHSA-2017:2004CVE reference · vendor-advisory, x_refsource_REDHAT
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.