CVE-2018-1000105 is a medium-severity (CVSS 4.3) CWE-863 vulnerability in com.sonyericsson.hudson.plugins.gerrit:gerrit-trigger. A fix is available for com.sonyericsson.hudson.plugins.gerrit:gerrit-trigger — see the affected versions and patch details below.
Incorrect Authorization in Jenkins Gerrit Trigger Plugin
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
com.sonyericsson.hudson.plugins.gerrit:gerrit-triggerReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
An 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 retrieve some configuration information about Gerrit in Jenkins.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.sonyericsson.hudson.plugins.gerrit:gerrit-trigger | all versions | 2.27.5com.sonyericsson.hudson.plugins.gerrit:gerrit-trigger:2.27.5 |
Affected Products
gerrit triggerjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.sonyericsson.hudson.plugins.gerrit:gerrit-trigger, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.sonyericsson.hudson.plugins.gerrit:gerrit-trigger to 2.27.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1000105 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2018-1000105 in your dependencies?
Find it across Maven, including transitive dependencies.