RapiddeployApplication · Jenkins
CVE-2019-16570
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 · uneditedA cross-site request forgery vulnerability in Jenkins RapidDeploy Plugin 4.1 and earlier allows attackers to connect to an attacker-specified web server.
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 confidenceA cross-site request forgery (CSRF) vulnerability in Jenkins RapidDeploy Plugin versions 4.1 and earlier allows remote attackers to trick authenticated users into causing the Jenkins server to connect to attacker-specified web servers. This could enable server-side request forgery (SSRF) attacks or exfiltration of sensitive data through the compromised Jenkins infrastructure.
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.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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 RapidDeploy plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or run: jenkins-cli.jar groovy = manager.plugins.each { if (it.shortName == 'rapiddeploy') println it }. The RapidDeploy plugin has shortName 'rapiddeploy'.Affected if The plugin appears in the installed list
-
Determine installed RapidDeploy versionIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed and locate RapidDeploy in the list to view the version column. Alternatively, via CLI: jenkins-cli.jar groovy = manager.plugins.find { it.shortName == 'rapiddeploy' }.versionAffected if A version number is displayed that is 4.1 or lower
-
Compare version against affected rangeCompare the installed version number to the affected range: versions 4.1 and earlier. If the version is 4.1, 4.0, 3.x or any lower number, it falls within the vulnerable range.Affected if Installed version is 4.1 or lower (e.g., 4.1, 4.0, 3.1, 1.0)
-
Confirm plugin is enabled and in useNavigate to Jenkins > Manage Jenkins > Configure System > look for RapidDeploy configuration section, or check job configurations that reference RapidDeploy. The vulnerability requires the plugin to be active.Affected if RapidDeploy configuration exists or jobs reference the plugin
Users are affected if the RapidDeploy plugin is installed and the version is 4.1 or earlier, regardless of whether it is actively configured.
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 RapidDeploy plugin to a version beyond 4.1 that contains the CSRF fix. If an updated version is unavailable, disable the plugin until a patched release is available.
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-2019-16570 — 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-2019-16570 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