Skip to content
Noroxi
CVE-2017-14867· NVD / CVE Program· CNA mitre

Git before 2.10.5, 2.11.x before 2.11.4, 2.12.x before 2.12.5, 2.13.x before 2.13.6, and 2.14.x before 2.14.2 uses unsafe Perl scripts to su

Git before 2.10.5, 2.11.x before 2.11.4, 2.12.x before 2.12.5, 2.13.x before 2.13.6, and 2.14.x before 2.14.2 uses unsafe Perl scripts to support subcommands such as cvsserver, which allows attackers to execute arbitrary OS commands via shell metacharacters in a module name. The vulnerable code is reachable via git-shell even without CVS support.

HighCVSS 8.8 · v3.0—No exploit Fix available
Published
Sep 28, 2017
Updated
Jun 16, 2026
EPSS
36.0% · 98th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

46

Plan

Add it to your regular patch cycle.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
11 / 30 · 36.0%

Affected systems

VendorProduct
git-scmgit
debiandebian linux

Affected versions

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

  • debian debian linux8.0
  • debian debian linux9.0
  • git-scm gitup to 2.10.4 inclusive
  • git-scm git2.11.0
  • git-scm git2.11.1
  • git-scm git2.11.2
  • git-scm git2.11.3
  • git-scm git2.12.0
  • git-scm git2.12.1
  • git-scm git2.12.2
  • git-scm git2.12.3
  • git-scm git2.12.4
  • git-scm git2.13.0
  • git-scm git2.13.1
  • git-scm git2.13.2
  • git-scm git2.13.3
  • git-scm git2.13.4
  • git-scm git2.13.5
  • git-scm git2.14.0
  • git-scm git2.14.1

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12gitbefore 1:2.14.2-11:2.14.2-1
Debian:7gitbefore 1:1.7.10.4-1+wheezy61:1.7.10.4-1+wheezy6
Debian:8gitbefore 1:2.1.4-2.1+deb8u51:2.1.4-2.1+deb8u5
Debian:9gitbefore 1:2.11.0-3+deb9u21:2.11.0-3+deb9u2
openSUSE:Tumbleweedgitbefore 2.33.0-1.32.33.0-1.3
SUSE:Linux Enterprise Software Development Kit 11 SP4gitbefore 1.7.12.4-0.18.6.11.7.12.4-0.18.6.1
SUSE:Linux Micro 6.0gitbefore 2.45.1-1.12.45.1-1.1
SUSE:OpenStack Cloud 6gitbefore 2.12.3-27.9.12.12.3-27.9.1

Other highest-scoring records for the same primary product.

  • CVE-2018-17456Git before 2.14.5, 2.15.x before 2.15.3, 2.16.x before 2.16.5, 2.17.x before 2.17.2, 2.18.x before 2.18.1, and 2.19.x before 2.19.1 allows r
    68This week
  • CVE-2025-48384Git allows arbitrary code execution through broken config quotingKEV
    63This week
  • CVE-2017-1000117A malicious third-party can give a crafted "ssh://..." URL to an unsuspecting victim, and an attempt to visit the URL can result in any prog
    58Plan
  • CVE-2021-21300malicious repositories can execute remote code while cloning
    57Plan
  • CVE-2022-23521gitattributes parsing integer overflow in git
    56Plan
  • CVE-2022-41903Integer overflow in `git archive`, `git log --format` leading to RCE in git
    52Plan

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
debian:git1:2.14.2-1 · Debian:12Package registry (OSV)
opensuse:git2.33.0-1.3 · openSUSE:TumbleweedPackage registry (OSV)
suse:git1.7.12.4-0.18.6.1 · SUSE:Linux Enterprise Software Development Kit 11 SP4Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No dated events beyond publication.

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.

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.

No nightly-computed relations.

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.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const host = req.body.host;exec("ping -c 1 " + host, onResult);

Fixed

ts
const host = req.body.host;if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);execFile("ping", ["-c", "1", host], onResult);

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

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

References

All records