Harvest ScmApplication · Jenkins
CVE-2020-2130
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 Harvest SCM Plugin 0.5.1 and earlier stores a 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 · moderate confidenceJenkins Harvest SCM Plugin 0.5.1 and earlier stores a password in plain text within its global configuration file on the Jenkins master filesystem. Any user with access to the master file system can read this configuration file and obtain the password in unencrypted form.
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
Harvest ScmApplication
<= 0.5.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
- 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 Harvest SCM Plugin is installedNavigate to Manage Jenkins -> Manage Plugins -> Installed tab, or list files in $JENKINS_HOME/plugins/ directory. Look for a plugin named 'Harvest SCM' or a .jpi file starting with 'harvest'.Affected if The Harvest SCM Plugin is present in the Jenkins environment.
-
Check installed plugin versionIn the Jenkins UI plugin manager, find the Harvest SCM Plugin and note the version number. Alternatively, inspect the plugin manifest file at $JENKINS_HOME/plugins/harvest.jpi/MANIFEST.MF or look for version in the .jpi file name.Affected if The installed version is 0.5.1 or any earlier version (0.5.1, 0.5.0, etc.).
-
Locate plugin global configuration fileCheck the Jenkins master filesystem for the configuration file. Standard path is $JENKINS_HOME/hudson.plugins.harvest.HarvestScm.xml. Also verify via Jenkins UI at Manage Jenkins -> Configure System -> look for Harvest SCM section.Affected if A configuration file for the Harvest SCM Plugin exists on the Jenkins master.
-
Inspect configuration for plain text passwordOpen the configuration file found (e.g., $JENKINS_HOME/hudson.plugins.harvest.HarvestScm.xml) and search for password-related XML elements. Look for password, repositoryPassword, or similar fields. Read the content of these fields.Affected if The password field contains an unencrypted, plain text value (not a Jenkins credential ID reference or encrypted string).
The environment is affected if the Harvest SCM Plugin version is 0.5.1 or earlier AND the plugin's global configuration file contains a password stored in plain text rather than as a credential ID.
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 dataMigrate the stored password to Jenkins' built-in credentials store or update to a plugin version that properly encrypts credentials at rest.
Fix this in Harvest Scm
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,032.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2130 — 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-2130 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