MesosApplication · Apache
CVE-2018-1000420
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 Mesos Plugin 0.17.1 and earlier in MesosCloud.java that allows attackers with Overall/Read access to obtain credentials IDs for credentials stored in Jenkins.
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 Mesos Plugin 0.17.1 and earlier contains an improper authorization vulnerability in MesosCloud.java where the plugin exposes credential IDs to any user with Overall/Read access, bypassing proper permission checks that should restrict credential enumeration to users with appropriate privileges.
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
MesosApplication
<= 0.17.1CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 Mesos Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed and look for 'Mesos' in the list, or use the CLI: jenkins-cli.jar or API to list installed pluginsAffected if The Mesos plugin appears in the installed plugins list
-
Check Mesos Plugin versionIn the installed plugins list, note the version number of the Mesos plugin. Compare this to the affected version range: 0.17.1 and earlierAffected if The installed version is 0.17.1 or any earlier version (e.g., 0.17.0, 0.16, etc.)
-
Verify MesosCloud configuration existsNavigate to Jenkins > Manage Jenkins > Configure Systems and look for a 'Mesos Cloud' or 'Mesos' configuration section, or inspect the configuration XML via Jenkins API at /api/json?tree=clouds[*,*]Affected if A Mesos Cloud configuration is present with credential settings defined
-
Check user access levelsNavigate to Jenkins > Manage Jenkins > Manage Users and review who has Overall/Read permission, or inspect authorization matrix at /api/json?tree=authorizationStrategy[*,*]Affected if Any untrusted or unauthorized users are granted Overall/Read access to the Jenkins instance
You are affected if the Mesos Plugin version is 0.17.1 or earlier AND a Mesos Cloud is configured with credentials AND untrusted users have Overall/Read access to the Jenkins instance.
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 Mesos Plugin to version 0.17.2 or later which implements proper authorization checks before returning credential IDs. If immediate upgrade is not possible, restrict Overall/Read access to trusted users only.
Fix this in Mesos
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-1000420 — 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-1000420 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