Jenkins ReviewbotApplication · Jenkins
CVE-2019-10278
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 jenkins-reviewbot Plugin in the ReviewboardDescriptor#doTestConnection form validation method allows attackers to initiate a connection to an attacker-specified 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 CSRF vulnerability in the Jenkins jenkins-reviewbot plugin's ReviewboardDescriptor#doTestConnection form validation method allows attackers to trigger authenticated users to initiate connections to attacker-controlled servers via forged requests.
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
Jenkins ReviewbotApplication
all versionsCVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 jenkins-reviewbot plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or run this Groovy script in Manage Jenkins > Script Console: Jenkins.instance.pluginManager.plugins.each { if (it.shortName == 'jenkins-reviewbot') { println "Plugin found: ${it.displayName}, Version: ${it.version}" } }Affected if The plugin named 'jenkins-reviewbot' appears in the installed plugins list or the script returns plugin information
-
Confirm plugin is enabledCheck the plugin status in Manage Jenkins > Manage Plugins > Installed tab, or run: Jenkins.instance.getPlugin('jenkins-reviewbot')?.enabledAffected if The plugin shows as 'Enabled' or the script returns true
-
Verify plugin functionality is accessibleNavigate to Jenkins > Manage Jenkins > Configure System and look for the Reviewbot configuration section (Reviewboard settings), or access the form validation endpoint at: /descriptor/reviewbot.ReviewboardDescriptor/doTestConnectionAffected if The Reviewbot configuration section exists and is accessible to authenticated users
-
Check global CSRF protectionNavigate to Jenkins > Manage Jenkins > Configure Global Security and verify 'Enable CSRF Protection' is checked, or run: Jenkins.instance.getCrumbIssuer() != nullAffected if CSRF protection is disabled or no crumb issuer is configured (Jenkins default CSRF protection may not fully mitigate this plugin-specific flaw)
If the jenkins-reviewbot plugin is installed and enabled, and the Reviewboard configuration form is accessible, the environment is affected by this CSRF vulnerability since all versions are vulnerable.
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 to a patched version of the jenkins-reviewbot plugin. If no patch is available, disable the plugin. Additionally, ensure Jenkins global CSRF protection is enabled.
Fix this in Jenkins Reviewbot
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10278 — 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-10278 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