ArtifactoryApplication · Jfrog
CVE-2018-1000424
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 insufficiently protected credentials vulnerability exists in Jenkins Artifactory Plugin 2.16.1 and earlier in ArtifactoryBuilder.java, CredentialsConfig.java that allows attackers with local file system access to obtain old credentials configured for the plugin before it integrated with Credentials Plugin.
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 Artifactory Plugin versions 2.16.1 and earlier stored credentials in an insecure manner in ArtifactoryBuilder.java and CredentialsConfig.java. Credentials that were configured before the plugin integrated with the Credentials Plugin were stored in a way that allowed local attackers with file system access to retrieve them in plaintext.
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
ArtifactoryApplication
<= 2.16.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
- 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.
-
Identify Artifactory Plugin installationIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed and look for 'Artifactory Plugin' in the list, or query the Jenkins plugin manager API for the artifactory-plugin versionAffected if The plugin is installed and its version is 2.16.1 or earlier
-
Locate plugin configuration filesNavigate to the Jenkins home directory and locate configuration files related to Artifactory, typically found in $JENKINS_HOME/org.jfrog.*.xml or similar paths containing 'artifactory' in the filenameAffected if Configuration files exist and were created or modified before the plugin integrated with the Credentials Plugin (approximately version 2.14.0-2.15.0 range)
-
Inspect stored credentialsExamine the ArtifactoryBuilder.xml or CredentialsConfig.xml configuration files in the Jenkins home directory for credential entries. Look for Base64-encoded or plaintext credential values in fields such as 'password', 'secret', or 'apiKey'Affected if Credentials appear in plaintext or are stored without integration with Jenkins' native Credentials Plugin mechanism
You are affected if the Jenkins Artifactory Plugin version is 2.16.1 or earlier and credentials were configured using the pre-Credentials-Plugin method, making them retrievable by anyone with file system access to the Jenkins configuration directory.
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 Jenkins Artifactory Plugin to a version newer than 2.16.1 and rotate all credentials that may have been stored using the vulnerable configuration, as they could have been compromised.
Fix this in Artifactory
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000424 — 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-1000424 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