ArtifactoryApplication · Jfrog
CVE-2020-2164
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 · uneditedJenkins Artifactory Plugin 3.5.0 and earlier stores its Artifactory server password unencrypted in its global configuration file on the Jenkins master where it can be viewed by users with access to the master file system.
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 3.5.0 and earlier stores the Artifactory server password unencrypted in plaintext in its global configuration file on the Jenkins master. Users with access to the master file system can directly view the password.
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
<= 3.5.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
- 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.
-
Verify Artifactory Plugin is installedAccess Jenkins manage plugins page or check $JENKINS_HOME/plugins/ for the artifactory plugin directoryAffected if The Artifactory plugin is present in the Jenkins installation
-
Check installed plugin versionView the plugin version in Jenkins plugin manager or inspect the plugin's MANIFEST.MF file in $JENKINS_HOME/plugins/Affected if The version is 3.5.0 or earlier
-
Locate the plugin's global configuration fileSearch for the Artifactory plugin configuration file in $JENKINS_HOME/, commonly found in a file named org.jfrog.hudson.ArtifactoryPlugin.xml or similar under the jenkins home directoryAffected if A configuration file for the Artifactory plugin exists
-
Inspect configuration file for plaintext passwordOpen the configuration file and look for password fields in the server configuration sectionAffected if The password value appears in plaintext (not encrypted, base64 encoded, or masked) in the configuration file
The environment is affected if the Jenkins Artifactory Plugin version is 3.5.0 or earlier and the configuration file contains unencrypted passwords in plaintext.
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 that encrypts stored passwords, and rotate any potentially exposed Artifactory server credentials as a precautionary measure.
Fix this in Artifactory
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-2020-2164 — 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-2020-2164 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