Container Image ScannerApplication · Anchore
CVE-2018-1999033
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 exposure of sensitive information vulnerability exists in Jenkins Anchore Container Image Scanner Plugin 10.16 and earlier in AnchoreBuilder.java that allows attackers with Item/ExtendedRead permission or file system access to the Jenkins master to obtain the password stored in this plugin's configuration.
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 Anchore Container Image Scanner Plugin version 10.16 and earlier stores credentials (password) in its configuration. Due to insufficient access controls in AnchoreBuilder.java, users with Item/ExtendedRead permission or direct filesystem access to the Jenkins master can retrieve this stored password, resulting in credential exposure.
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
Container Image ScannerApplication
<= 1.0.16CVSS 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.1/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.
-
Identify if Anchore Container Image Scanner Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Anchore' or check the $JENKINS_HOME/plugins directory for the anchore-pluginAffected if The plugin is present in the list of installed plugins
-
Determine the installed plugin versionIn Jenkins > Manage Jenkins > Manage Plugins > Installed tab, locate the Anchore Container Image Scanner Plugin and note the version number displayedAffected if The version is 10.16 or earlier, or version 1.0.16 or earlier (version scheme may vary)
-
Locate stored credentials in plugin configurationExamine the Jenkins configuration XML files in $JENKINS_HOME/jobs/<job-name>/config.xml or global configuration in $JENKINS_HOME/org.jenkinsci.plugins.anchore.Config.xml for the presence of a <password> or <credentials> element within the Anchore plugin sectionAffected if A password or credential field is present and stored in plaintext within the configuration file
-
Verify access control on configuration filesCheck file system permissions on Jenkins configuration directories and review Job permissions in Jenkins > Manage Jenkins > Configure Global Security to see which users or groups have Item/ExtendedRead permissionsAffected if Users with Item/ExtendedRead permission exist or configuration files are readable by non-admin users
A user is affected if the Anchore Container Image Scanner Plugin version 10.16 or earlier (or 1.0.16 or earlier) is installed AND credentials are stored in the plugin configuration AND users with Item/ExtendedRead permission or filesystem access can read those configurations.
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 the Anchore Container Image Scanner Plugin to a version later than 10.16. Additionally, restrict Item/ExtendedRead permissions to only trusted users and ensure filesystem access controls are properly configured.
Fix this in Container Image Scanner
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-1999033 — 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-1999033 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