dbcve.org
Gerrit TriggerApplication · Jenkins

CVE-2019-16551

HIGH · 8.8 CVSS v3.1 Published 2019-12-17
Fix available
A fix is available. Upgrade to after 2.30.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 cross-site request forgery vulnerability in Jenkins Gerrit Trigger Plugin 2.30.1 and earlier allows attackers to connect to an attacker-specified HTTP URL or SSH server using attacker-specified credentials.

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

CSRF vulnerability in Jenkins Gerrit Trigger Plugin 2.30.1 and earlier allows authenticated administrators to be tricked into making unintended connections to attacker-specified HTTP URLs or SSH servers using attacker-supplied credentials. The flaw exploits the lack of proper CSRF token validation on plugin endpoints.

MitigationUpdate Jenkins Gerrit Trigger Plugin to version 2.30.2 or later. If immediate update is not possible, restrict admin access to trusted networks and monitor for suspicious outbound connections.

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
Gerrit TriggerApplication
Affected:<= 2.30.1

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
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 checks

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

  1. Verify Jenkins Gerrit Trigger plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for Gerrit Trigger, or check the plugin directory at $JENKINS_HOME/plugins/gerrit-trigger/
    Affected if The Gerrit Trigger plugin appears in the installed plugins list or the plugin directory exists
  2. Check the installed Gerrit Trigger plugin version
    In Jenkins plugin manager, locate Gerrit Trigger in the Installed tab and read the version column, or inspect the plugin manifest file (MANIFEST.MF or manifest.json) inside the plugin directory
    Affected if Version is 2.30.1 or lower
  3. Confirm the plugin is enabled and configured
    Navigate to Manage Jenkins > Gerrit Trigger > Configuration or check Jenkins configuration files for gerrit-trigger configuration blocks
    Affected if The Gerrit Trigger configuration is present and the plugin is active in the Jenkins instance

User is affected if Jenkins Gerrit Trigger plugin version 2.30.1 or earlier is installed and the plugin is enabled in their Jenkins environment

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
Upgrade available Upgrade to a release after 2.30.1
Interim mitigation

Update Jenkins Gerrit Trigger Plugin to version 2.30.2 or later. If immediate update is not possible, restrict admin access to trusted networks and monitor for suspicious outbound connections.

Fix this in Gerrit Trigger Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-16551 — 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-16551 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