GitApplication · Jenkins
CVE-2018-1000110
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 · uneditedAn improper authorization vulnerability exists in Jenkins Git Plugin version 3.7.0 and earlier in GitStatus.java that allows an attacker with network access to obtain a list of nodes and users.
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 Plugin versions 3.7.0 and earlier contain an improper authorization vulnerability in GitStatus.java. An attacker with network access can exploit this flaw to obtain a list of Jenkins nodes and users without proper authorization, leading to information disclosure.
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
<= 3.7.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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.
-
Check Jenkins Git Plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed tab, or check the jenkins.war manifest. Look for 'Git Plugin' in the plugin list and note the version number.Affected if The Git Plugin version is 3.7.0 or lower (any version up to and including 3.7.0).
-
Verify Git Plugin is installed and enabledGo to Manage Jenkins > Manage Plugins > Installed and confirm the Git Plugin shows as 'Enabled' or 'Active' in the status column.Affected if The Git Plugin is installed and enabled (the vulnerability only affects installations where the plugin is active).
-
Check if the Git status endpoint is network-accessibleAttempt to access http://[jenkins-url]/git/ (or /git/notifyCommit or similar Git-related endpoints). From an untrusted network location, see if HTTP requests to these endpoints return node or user information without authentication.Affected if The /git/ status endpoint responds without requiring authentication and returns Jenkins node or user data.
-
Confirm authorization configurationReview Manage Jenkins > Configure Global Security > Authorization settings. Check whether anonymous users have read access or if the Git status endpoint permits unauthenticated requests.Affected if Anonymous or unauthenticated users can access Jenkins data, or the Git status endpoint is not protected by authentication/authorization checks.
You are affected if the Jenkins Git Plugin version is 3.7.0 or earlier AND the plugin is enabled AND the Git status endpoint is accessible without authentication on your network.
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 Plugin to a version higher than 3.7.0 to remediate this authorization bypass. Alternatively, restrict network access to the Jenkins management interface.
Fix this in Git
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000110 — 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-2018-1000110 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