MercurialApplication · Jenkins
CVE-2018-1000112
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 Mercurial Plugin version 2.2 and earlier in MercurialStatus.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 confidenceJenkins Mercurial Plugin versions 2.2 and earlier contain an improper authorization vulnerability in MercurialStatus.java that allows unauthenticated attackers with network access to enumerate and obtain lists of Jenkins nodes and user accounts.
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
MercurialApplication
<= 2.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.
-
Identify installed Mercurial Plugin versionNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and locate the Mercurial Plugin, or check the $JENKINS_HOME/plugins/mercurial directory for the manifest fileAffected if The installed version is 2.2 or earlier (versions prior to 2.2.1)
-
Verify status endpoint accessibilityAttempt an unauthenticated HTTP request to the Mercurial status endpoint (typically /mercurial/status/ or /mercurial/credential/ endpoints) using curl or a browserAffected if The endpoint returns node or user account information without requiring authentication
-
Check plugin configurationNavigate to Jenkins > Manage Jenkins > Configure System > Mercurial > Advanced settings and examine if status reporting is enabledAffected if Status reporting is enabled and accessible without authentication
-
Review authorization matrixNavigate to Jenkins > Manage Jenkins > Configure Global Security and check if the Mercurial status URL is excluded from authentication requirementsAffected if The status endpoints are not protected by authorization or are set to anonymous access
A user is affected if they have Jenkins Mercurial Plugin version 2.2 or earlier installed with unauthenticated access to the Mercurial status endpoint.
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 Mercurial Plugin to version 2.2.1 or later. Additionally, restrict network access to Jenkins management interfaces and implement proper authorization checks for status endpoints.
Fix this in Mercurial
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000112 — 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-1000112 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