CoverityApplication · Jenkins
CVE-2018-1000104
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 plaintext storage of a password vulnerability exists in Jenkins Coverity Plugin 1.10.0 and earlier in CIMInstance.java that allows an attacker with local file system access or control of a Jenkins administrator's web browser (e.g. malicious extension) to retrieve the configured keystore and private key passwords.
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 confidenceThe Jenkins Coverity Plugin versions 1.10.0 and earlier stores keystore and private key passwords in plaintext within CIMInstance.java (or associated configuration files). An attacker with local filesystem access to the Jenkins server or with control over a Jenkins administrator's web browser (via malicious extension) can directly read these plaintext credentials.
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
CoverityApplication
<= 1.10.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 the installed Coverity Plugin versionNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and locate the Coverity Plugin, or check the plugin's .hpi file in the Jenkins plugins directory for the version manifestAffected if The version is 1.10.0 or lower
-
Locate Coverity plugin configuration filesSearch the Jenkins home directory for configuration files related to the Coverity plugin, typically found under $JENKINS_HOME/plugins/coverity/ or in job configuration XML filesAffected if Configuration files exist and contain Coverity-related settings
-
Inspect for plaintext passwords in Coverity configurationOpen the Coverity plugin configuration files and search for any plaintext strings matching keystore passwords, private key passwords, or similar credential fieldsAffected if Any keystore or private key passwords are stored in plaintext rather than encrypted or masked
-
Check CIMInstance.java source file if accessibleIf the Coverity plugin source is available in the plugins directory, examine CIMInstance.java for hardcoded or plaintext password storage patternsAffected if The CIMInstance.java file or associated configuration contains plaintext credentials
A user is affected if the Jenkins Coverity Plugin version is 1.10.0 or earlier AND plaintext passwords are found in the plugin's configuration files or the CIMInstance.java source file.
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 dataUpdate the Jenkins Coverity Plugin to a version newer than 1.10.0 which should implement proper credential encryption. Additionally, rotate any exposed keystore and private key passwords immediately, as they may have been compromised.
Fix this in Coverity
Scoped from the published advisory
- Consultation2.0 h
- Implementation6.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 $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000104 — 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-1000104 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