Gerrit TriggerApplication · Jenkins
CVE-2018-1000106
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 · uneditedAn improper authorization vulnerability exists in Jenkins Gerrit Trigger Plugin 2.27.4 and earlier in GerritManagement.java, GerritServer.java, and PluginImpl.java that allows an attacker with Overall/Read access to modify the Gerrit configuration in Jenkins.
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 confidenceThe Jenkins Gerrit Trigger Plugin before version 2.27.5 contains an improper authorization vulnerability where users with only Overall/Read permission (typically a read-only role) can modify Gerrit server configuration. The affected files GerritManagement.java, GerritServer.java, and PluginImpl.java lack proper permission checks before allowing configuration changes.
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.27.4CVSS 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
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
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.
-
Identify Gerrit Trigger Plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Gerrit Trigger', or use Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep -i gerritAffected if The installed version is 2.27.4 or lower
-
Verify if Gerrit server configuration is exposedNavigate to Manage Jenkins > Gerrit Management (or check if the Gerrit Trigger configuration page is accessible via URL path /jenkins/gerrit-management/). Try accessing this URL with a user account that has only Overall/Read permission.Affected if Users with only Overall/Read permission can access or view the Gerrit server configuration page
-
Check for unauthorized Gerrit server modificationsReview the Gerrit Trigger plugin configuration at Manage Jenkins > Gerrit Trigger > Gerrit Servers. Verify that configuration changes were made by accounts that should only have read access.Affected if Gerrit server settings have been modified by users who should only have Overall/Read permission
-
Audit user accounts with Overall/Read permissionNavigate to Manage Jenkins > Manage Users or review security matrix configurations to identify all users granted Overall/Read permission. Cross-reference with Gerrit configuration change logs.Affected if Multiple users have Overall/Read permission and the Gerrit Trigger plugin version is 2.27.4 or lower
The environment is affected if the Gerrit Trigger Plugin version is 2.27.4 or lower AND users with only Overall/Read permission can access or modify Gerrit server configuration settings.
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.27.5 or later which implements proper authorization checks. As a compensating control, restrict Overall/Read access to trusted users only until the upgrade is applied.
Fix this in Gerrit Trigger
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-2018-1000106 — 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-2018-1000106 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