dbcve.org
GitApplication · Jenkins

CVE-2017-1000092

HIGH · 7.5 CVSS v3.0 Published 2017-10-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Git Plugin connects to a user-specified Git repository as part of form validation. An attacker with no direct access to Jenkins but able to guess at a username/password credentials ID could trick a developer with job configuration permissions into following a link with a maliciously crafted Jenkins URL which would result in the Jenkins Git client sending the username and password to an attacker-controlled server.

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 confidence

The Jenkins Git Plugin performs form validation by connecting to user-specified Git repositories. An attacker who can guess a credentials ID could trick a developer with job configuration permissions into visiting a maliciously crafted Jenkins URL, causing Jenkins to transmit stored username/password credentials to an attacker-controlled server during the validation process.

MitigationUpgrade to Git Plugin version 3.0.0 or later which implements URL validation to prevent connections to attacker-controlled servers during form validation. Additionally, use non-predictable credentials IDs to reduce guessability.

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
GitApplication
Affected:= 0.1.0= 0.2.0= 0.3.0= 0.4.0= 0.5.0= 0.6.0= 0.7.0= 0.7.1= 0.7.2= 0.7.3= 0.8.0= 0.8.1

CVSS 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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Jenkins Git Plugin is installed
    Access Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'git', or run: Jenkins.instance.pluginManager.plugins.find { it.shortName == 'git' }
    Affected if The Git plugin is not found in the installed plugins list
  2. Determine the installed Git plugin version
    Check the plugin details page in Jenkins plugin manager, or execute: Jenkins.instance.pluginManager.plugins.find { it.shortName == 'git' }?.version
    Affected if The version is 0.1.0, 0.2.0, 0.3.0, 0.4.0, 0.5.0, 0.6.0, 0.7.0, 0.7.1, 0.7.2, 0.7.3, 0.8.0, or 0.8.1
  3. Check if credentials are stored in Jenkins
    Navigate to Credentials > System > Global credentials, or query via script: Jenkins.instance.getExtensionList('com.cloudbees.plugins.credentials.CredentialsStore').first().getCredentials()
    Affected if Any username/password credentials are stored in Jenkins credentials store
  4. Verify users with job configuration permissions exist
    Navigate to Manage Jenkins > Manage Users, or check job-level permissions via: Jenkins.instance.items.collect { it.permissions }
    Affected if There are users granted the ability to configure jobs, as the attack requires tricking such a user into visiting a malicious URL

You are affected if the Git plugin is installed with version 0.1.0 through 0.8.1 AND credentials are stored in Jenkins AND users with job configuration permissions exist in your environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Git Plugin version 3.0.0 or later which implements URL validation to prevent connections to attacker-controlled servers during form validation. Additionally, use non-predictable credentials IDs to reduce guessability.

Fix this in Git Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-1000092 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-1000092 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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