CVE-2018-1999030 — maven-artifact-choicelist…
MEDIUMFix: jenkinsci/maven-artifact-choicelistprovider-plugin@2d2e20cCVE-2018-1999030 is a medium-severity (CVSS 5.4) Information Exposure vulnerability in org.jenkins-ci.plugins:maven-artifact-choicelistprovider. A fix is available for org.jenkins-ci.plugins:maven-artifact-choicelistprovider — see the affected versions and patch details below.
Jenkins Maven Artifact ChoiceListProvider (Nexus) Plugin CSRF vulnerability and missing permission checks
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
org.jenkins-ci.plugins:maven-artifact-choicelistproviderReal-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 exposure of sensitive information vulnerability exists in Jenkins Maven Artifact ChoiceListProvider (Nexus) Plugin 1.3.1 and earlier in ArtifactoryChoiceListProvider.java, NexusChoiceListProvider.java, Nexus3ChoiceListProvider.java that allows attackers to capture credentials with a known credentials ID stored in Jenkins.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:maven-artifact-choicelistprovider | all versions | 1.3.2org.jenkins-ci.plugins:maven-artifact-choicelistprovider:1.3.2 |
Affected Products
maven artifact choicelistprovider \(nexus\)jenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:maven-artifact-choicelistprovider, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:maven-artifact-choicelistprovider to 1.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1999030 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is CVE-2018-1999030 in your dependencies?
Find it across Maven, including transitive dependencies.