SubversionApplication · Jenkins
CVE-2018-1000111
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 Subversion Plugin version 2.10.2 and earlier in SubversionStatus.java and SubversionRepositoryStatus.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 confidenceThis is an improper authorization vulnerability in Jenkins Subversion Plugin versions 2.10.2 and earlier. The affected files (SubversionStatus.java and SubversionRepositoryStatus.java) lack proper authorization checks, allowing any attacker with network access to retrieve sensitive information including lists of nodes and users without authentication.
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
SubversionApplication
<= 2.10.2CVSS 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.
-
Verify Jenkins Subversion Plugin is installedIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and look for 'Subversion' in the list of installed plugins.Affected if The Subversion plugin appears in the installed plugins list.
-
Determine the installed Subversion Plugin versionIn the Installed plugins list, note the version number shown next to the Subversion plugin. Alternatively, check the changelog or the plugin's manage page for the version.Affected if The installed version is 2.10.2 or any version lower than 2.10.2.
-
Confirm the Subversion status endpoints are accessibleAttempt to access the Subversion status-related URLs on your Jenkins instance. The vulnerability affects endpoints related to SubversionStatus.java and SubversionRepositoryStatus.java. Try accessing common paths like /subversion/ or paths that expose repository status information.Affected if The endpoints are reachable without requiring authentication.
-
Verify network accessibility of JenkinsDetermine if your Jenkins instance is exposed to the network without proper access restrictions. Check if the Jenkins web interface can be accessed from untrusted networks without authentication.Affected if Jenkins is accessible from networks without authentication and the Subversion plugin version is 2.10.2 or earlier.
You are affected if your Jenkins instance has the Subversion Plugin installed at version 2.10.2 or lower and the Subversion status endpoints are accessible without authentication to untrusted users.
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 Subversion Plugin to a version newer than 2.10.2. As a compensating control, implement network-level access restrictions to limit who can reach the Jenkins instance.
Fix this in Subversion
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000111 — 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-1000111 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