CryptomoveApplication · Jenkins
CVE-2020-2159
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 CryptoMove Plugin 0.1.33 and earlier allows attackers with Job/Configure access to execute arbitrary OS commands on the Jenkins master as the OS user account running Jenkins.
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 CryptoMove Plugin versions 0.1.33 and earlier contains a command injection vulnerability where attackers with Job/Configure permission can inject and execute arbitrary OS commands on the Jenkins master node, running with the same privileges as the Jenkins service account.
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
CryptomoveApplication
<= 0.1.33CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Verify CryptoMove plugin is installedLog into Jenkins as an administrator, navigate to Manage Jenkins > Manage Plugins > Installed tab, and search for 'CryptoMove' in the list of installed pluginsAffected if CryptoMove plugin appears in the installed plugins list
-
Check installed CryptoMove plugin versionIn the Installed plugins tab, locate the CryptoMove entry and note the Version column. Compare this version number against the affected range: any version 0.1.33 or earlier is vulnerableAffected if The installed version is 0.1.33 or earlier
-
Identify users with Job/Configure permissionNavigate to Manage Jenkins > Manage and Assign Users > Global Security or view Job configuration permissions. Check which users or groups are granted the 'Job/Configure' permission, which allows configuring job settingsAffected if Any untrusted or unauthenticated users have been granted Job/Configure permission
-
Review job configurations using CryptoMoveExamine any Jenkins jobs that utilize CryptoMove plugin functionality. Check job configuration pages for any CryptoMove-related build steps or configurationsAffected if Any jobs are configured with CryptoMove plugin features
A user is affected if the CryptoMove plugin version 0.1.33 or earlier is installed AND untrusted users have Job/Configure permission, allowing potential command injection execution.
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 CryptoMove Plugin to a version newer than 0.1.33, and restrict Job/Configure access to only trusted, authenticated users following least-privilege principles.
Fix this in Cryptomove
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2159 — 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-2159 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