dbcve.org
Jenkins ReviewbotApplication · Jenkins

CVE-2019-10279

MEDIUM · 6.5 CVSS v3.1 Published 2019-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A missing permission check in Jenkins jenkins-reviewbot Plugin in the ReviewboardDescriptor#doTestConnection form validation method allows attackers with Overall/Read permission 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 confidence

Missing permission check in Jenkins jenkins-reviewbot Plugin allows attackers with Overall/Read permission to trigger the ReviewboardDescriptor#doTestConnection method, causing the Jenkins server to initiate connections to attacker-specified servers. This enables SSRF attacks, internal network reconnaissance, and potential data exfiltration through the Jenkins server.

MitigationUpdate jenkins-reviewbot plugin to version containing proper permission checks, or remove the plugin if unused. Verify that form validation methods require appropriate permission levels beyond Overall/Read.

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
Affected:all versions

CVSS 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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if jenkins-reviewbot plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab. Search for 'jenkins-reviewbot' or 'Reviewbot' in the list of installed plugins.
    Affected if The plugin appears in the installed plugins list, indicating it is present in the environment
  2. Verify the plugin version
    In the Installed plugins tab, locate the jenkins-reviewbot plugin and check the Version column. Compare against the affected version range.
    Affected if Any version is installed since all versions of jenkins-reviewbot are affected by this vulnerability
  3. Check access to the form validation endpoint
    Identify if the ReviewboardDescriptor#doTestConnection endpoint is accessible. This is typically exposed at /descriptorByName/jenkins_reviewbot.ReviewboardDescriptor/testConnection or similar paths under /descriptorByName/. Check routing configuration or attempt a GET request to these endpoints.
    Affected if The form validation endpoint responds without requiring permissions beyond Overall/Read, indicating the SSRF vulnerability is present
  4. Inspect permission configuration for form validation methods
    Review the plugin's source code or configuration files for @Restricted or permission annotations on the doTestConnection method. In Jenkins, check if the descriptor's form validation requires HigherLevel permission or is annotated appropriately.
    Affected if The doTestConnection method lacks proper permission checks (such as @RequirePOST with appropriate permission requirements) and is accessible to users with only Overall/Read access
  5. Confirm plugin is in use
    Check Jenkins job configurations, system configuration, or any build steps that reference jenkins-reviewbot or Reviewboard integration.
    Affected if The plugin is actively configured in Jenkins jobs or system settings, meaning the vulnerable code path could be triggered

If the jenkins-reviewbot plugin is installed and its form validation endpoint is accessible without elevated permissions, the environment is vulnerable to CVE-2019-10279 SSRF attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update jenkins-reviewbot plugin to version containing proper permission checks, or remove the plugin if unused. Verify that form validation methods require appropriate permission levels beyond Overall/Read.

Fix this in Jenkins Reviewbot Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-10279 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-10279 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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