dbcve.org
MesosApplication · Apache

CVE-2018-1000421

MEDIUM · 6.5 CVSS v3.0 Published 2019-01-09
Fix available
A fix is available. Upgrade to after 0.17.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
An improper authorization vulnerability exists in Jenkins Mesos Plugin 0.17.1 and earlier in MesosCloud.java that allows attackers with Overall/Read access to initiate a test connection to an attacker-specified Mesos server with attacker-specified credentials IDs obtained through another method, capturing 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 confidence

Improper authorization in Jenkins Mesos Plugin allows users with Overall/Read access (lowest privilege) to trigger test connections to attacker-specified Mesos servers using credential IDs obtained through other vulnerabilities or misconfigurations. This enables credential harvesting by proxying authentication attempts through Jenkins to capture stored credentials.

MitigationUpgrade Jenkins Mesos Plugin to version 0.17.2 or later which includes proper authorization checks. Additionally, restrict Overall/Read access and audit credential storage configurations.

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
Affected:<= 0.17.1

CVSS 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
None
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Jenkins Mesos Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or check the $JENKINS_HOME/plugins directory for mesos folder
    Affected if The Mesos Plugin is present in the Jenkins installation
  2. Determine the installed Mesos Plugin version
    In Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab and locate Mesos Plugin to view the version number
    Affected if The version is 0.17.1 or earlier (verify against the vulnerable version range)
  3. Check for configured Mesos cloud configurations
    Navigate to Manage Jenkins > Configure System and look for Mesos Cloud section, or inspect $JENKINS_HOME/org.jenkinsci.plugins.mesos.MesosCloud.xml
    Affected if One or more Mesos cloud configurations exist with credential references
  4. Review stored Mesos credentials
    Go to Credentials > System > Global credentials, or check the credentials.xml file in $JENKINS_HOME, looking for Mesos-related credential entries
    Affected if Any Mesos credentials (usernames, passwords, SSH keys, or token credentials) are stored in Jenkins
  5. Inspect Overall/Read permission assignments
    Go to Manage Jenkins > Configure Global Security > Authorization section, or review config.xml for the authorization strategy setting
    Affected if The authorization matrix allows Overall/Read permission to users other than administrators

You are affected if Jenkins Mesos Plugin version 0.17.1 or earlier is installed AND Mesos cloud credentials are configured, regardless of authorization settings, because the vulnerability allows any user with basic Read access to trigger connection tests using stored credential IDs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 0.17.1
Interim mitigation

Upgrade Jenkins Mesos Plugin to version 0.17.2 or later which includes proper authorization checks. Additionally, restrict Overall/Read access and audit credential storage configurations.

Fix this in Mesos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1000421 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1000421 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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