GitApplication · Jenkins
CVE-2018-1000182
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 · uneditedA server-side request forgery vulnerability exists in Jenkins Git Plugin 3.9.0 and older in AssemblaWeb.java, GitBlitRepositoryBrowser.java, Gitiles.java, TFS2013GitRepositoryBrowser.java, ViewGitWeb.java that allows attackers with Overall/Read access to cause Jenkins to send a GET request to a specified URL.
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 confidenceA Server-Side Request Forgery (SSRF) vulnerability in Jenkins Git Plugin versions 3.9.0 and older allows authenticated attackers with Overall/Read access to force Jenkins to send arbitrary GET requests to attacker-controlled URLs via multiple repository browser implementation files (AssemblaWeb.java, GitBlitRepositoryBrowser.java, Gitiles.java, TFS2013GitRepositoryBrowser.java, ViewGitWeb.java).
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.9.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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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 installed Jenkins Git Plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Git Plugin', or check the file $JENKINS_HOME/plugins/git/WEB-INF/lib/jenkins-git-plugin-*.jar or use the CLI: java -jar jenkins-cli.jar -s http://localhost:8080/ list-plugins | grep -i gitAffected if The installed version is 3.9.0 or older
-
Verify if repository browsers are configuredCheck job configurations that use Git for repository browser settings. Look for Assembla, GitBlit, Gitiles, TFS2013, or ViewGitWeb browser types in job configuration XML files in $JENKINS_HOME/jobs/<jobname>/config.xml, or inspect via UI at each job's configuration page under Source Code Management > Git > Repository BrowserAffected if Any Git job has one of the affected repository browser types (AssemblaWeb, GitBlitRepositoryBrowser, Gitiles, TFS2013GitRepositoryBrowser, or ViewGitWeb) enabled
-
Check user permission model for Overall/Read accessNavigate to Manage Jenkins > Manage Users and review user accounts, or check authorization configuration at Manage Jenkins > Configure Global Security to see which users or groups have Overall/Read permissionsAffected if There are user accounts or groups with Overall/Read permission that are not fully trusted, as this permission level is required to exploit the vulnerability
A user is affected if their Jenkins Git Plugin version is 3.9.0 or older AND they have repository browsers configured AND there are users with Overall/Read access present in the system.
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 version 3.10.0 or newer to remediate this vulnerability. Restrict Overall/Read access permissions as an interim control if upgrading is not immediately feasible.
Fix this in Git
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000182 — 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-1000182 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