Git ClientApplication · Jenkins
CVE-2019-10392
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJenkins Git Client Plugin 2.8.4 and earlier and 3.0.0-rc did not properly restrict values passed as URL argument to an invocation of 'git ls-remote', resulting in OS command injection.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Jenkins Git Client Plugin versions 2.8.4 and earlier and 3.0.0-rc fail to properly sanitize URL inputs passed to the git ls-remote command, allowing attackers to inject arbitrary OS commands through maliciously crafted repository URLs.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Git ClientApplication
<= 2.8.4= 3.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the Jenkins Git Client Plugin installation directoryNavigate to the Jenkins plugins directory (typically $JENKINS_HOME/plugins/) and look for a directory named 'git-client' or check through the Jenkins web UI at Manage Jenkins > Manage Plugins > Installed tabAffected if The plugin directory or entry does not exist, meaning the plugin is not installed (not affected in this case, proceed to check version)
-
Determine the installed version of the Git Client PluginCheck the version file inside the plugin directory (e.g., META-INF/MANIFEST.MF or the manifest.json) or view the version column in Jenkins web UI at Manage Jenkins > Manage Plugins > InstalledAffected if You cannot determine the version (plugin may not be installed)
-
Compare the installed version against the affected rangeCompare the version you found to the affected versions: any version <= 2.8.4 or version 3.0.0 exactlyAffected if The installed version is 2.8.4 or lower, OR the installed version is exactly 3.0.0, indicating the environment is vulnerable to command injection through git ls-remote
-
Verify if git ls-remote is used in Jenkins jobsReview Jenkins job configurations that use Git, particularly those using the Git Client Plugin method 'Git Remote' or similar features that invoke ls-remoteAffected if Jobs use Git with the affected plugin version and connect to external repositories, making the command injection exploit possible
If the Jenkins Git Client Plugin version is 2.8.4 or lower, or exactly 3.0.0, and jobs using git ls-remote are configured, the environment is vulnerable to OS command injection via malicious repository URLs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Jenkins Git Client Plugin to a patched version that implements proper URL input validation and sanitization before passing to git ls-remote.
Fix this in Git Client
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10392 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10392 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data