RapiddeployApplication · Jenkins
CVE-2020-2170
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 RapidDeploy Plugin 4.2 and earlier does not escape package names in the table of packages obtained from a remote server, resulting in a stored XSS vulnerability.
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 RapidDeploy Plugin versions 4.2 and earlier are vulnerable to stored XSS because package names retrieved from a remote server are displayed in an HTML table without proper escaping. An attacker who controls the remote server can inject malicious JavaScript through crafted package names that will execute in the browsers of users viewing the package table.
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
RapiddeployApplication
<= 4.2CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 RapidDeploy plugin versionNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, locate the RapidDeploy plugin and check the Version columnAffected if Version is 4.2 or earlier (any version listed as 4.2 or lower)
-
Confirm RapidDeploy is installedVerify the RapidDeploy plugin appears in the installed plugins list at Manage Jenkins > Manage Plugins > InstalledAffected if Plugin is present in the installed plugins list
-
Check for remote deployment server configurationNavigate to Manage Jenkins > Configure System > look for RapidDeploy configuration section; check if a remote deployment server URL is configured under the RapidDeploy settingsAffected if A remote server URL is configured in the RapidDeploy plugin settings
-
Verify package retrieval feature usageAccess the RapidDeploy project/job configuration or a deployed package view page where package names from the remote server would be displayed in an HTML tableAffected if The package table view is accessible and displays package names retrieved from a configured remote server
You are affected if the RapidDeploy plugin version is 4.2 or earlier AND a remote deployment server is configured such that package names from that server are displayed to users in the Jenkins interface.
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 RapidDeploy Plugin to version 4.3 or later. Until the patch is applied, restrict access to trusted remote deployment servers and minimize user access to the affected functionality.
Fix this in Rapiddeploy
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2170 — 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-2170 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