Gerrit TriggerApplication · Jenkins
CVE-2019-16552
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 missing permission check in Jenkins Gerrit Trigger Plugin 2.30.1 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified HTTP URL or SSH server using attacker-specified credentials, or determine the existence of a file with a given path on the Jenkins master.
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 confidenceJenkins Gerrit Trigger Plugin versions 2.30.1 and earlier lack proper permission checks, allowing any user with basic Overall/Read access to trigger HTTP or SSH connections to attacker-controlled endpoints, and to probe for file existence on the Jenkins master filesystem.
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
<= 2.30.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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.
-
Verify Gerrit Trigger Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar -s http://localhost:8080 list-pluginsAffected if Gerrit Trigger plugin appears in the installed plugins list
-
Identify installed Gerrit Trigger Plugin versionIn Manage Plugins > Installed tab, find the Gerrit Trigger entry and note the Version column. Alternatively, check the plugin's manifest file at $JENKINS_HOME/plugins/gerrit-trigger/META-INF/MANIFEST.MFAffected if Version is 2.30.1 or earlier
-
Compare version against affected rangeReview the version found against the vulnerable range: any version <= 2.30.1 is affectedAffected if Installed version is 2.30.1 or lower, or version cannot be determined but plugin is present
-
Confirm user access configurationNavigate to Jenkins > Manage Jenkins > Manage Users, and review which users exist. Check Jenkins > Configure Global Security to see if Overall/Read permission is granted to authenticated users or anonymous usersAffected if Untrusted or unauthenticated users have Overall/Read access to the Jenkins instance
You are affected if the Gerrit Trigger Plugin is installed at version 2.30.1 or earlier and your Jenkins instance grants Overall/Read access to users who should not have the ability to trigger external connections or probe filesystem paths.
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 Jenkins Gerrit Trigger Plugin to version 2.30.2 or later to obtain the missing permission checks.
Fix this in Gerrit Trigger
Scoped from the published advisory
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16552 — 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-16552 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