dbcve.org
Maven Artifact Choicelistprovider \(nexus\)Application · Jenkins

CVE-2018-1999030

MEDIUM · 5.4 CVSS v3.0 Published 2018-08-01
Fix available
A fix is available. Upgrade to after 1.3.1 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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

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 · moderate confidence

The Maven Artifact ChoiceListProvider plugin for Jenkins versions 1.3.1 and earlier contains an information disclosure vulnerability in ArtifactoryChoiceListProvider.java, NexusChoiceListProvider.java, and Nexus3ChoiceListProvider.java. The vulnerability allows attackers to capture credentials stored in Jenkins when they have knowledge of a specific credentials ID.

MitigationUpgrade the Maven Artifact ChoiceListProvider plugin to a version newer than 1.3.1. Additionally, review and rotate any credentials that may have been exposed or could be targeted using this vulnerability.

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
Maven Artifact Choicelistprovider \(nexus\)Application
Affected:<= 1.3.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/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 checks

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

  1. Check if Maven Artifact ChoiceListProvider plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Maven Artifact ChoiceListProvider' or 'nexus' to locate the plugin
    Affected if The plugin is listed in the installed plugins
  2. Identify the installed version of the plugin
    In the Installed Plugins tab, locate the Maven Artifact ChoiceListProvider plugin and note the Version column. Alternatively, check the plugin's POM file or manifest if accessible through the Jenkins plugin directory
    Affected if The version is 1.3.1 or earlier
  3. Verify if ArtifactoryChoiceListProvider is configured
    Review Jenkins job configurations or system configuration for any use of ArtifactoryChoiceListProvider. Check job configuration XML files or navigate to Jenkins > Manage Jenkins > Configure System for any Artifactory-related plugin configurations
    Affected if ArtifactoryChoiceListProvider is configured with stored credentials
  4. Verify if NexusChoiceListProvider is configured
    Review Jenkins job configurations or system configuration for any use of NexusChoiceListProvider. Check job configuration XML files or navigate to Jenkins > Manage Jenkins > Configure System for Nexus-related plugin configurations
    Affected if NexusChoiceListProvider is configured with stored credentials
  5. Verify if Nexus3ChoiceListProvider is configured
    Review Jenkins job configurations or system configuration for any use of Nexus3ChoiceListProvider. Check job configuration XML files or navigate to Jenkins > Manage Jenkins > Configure System for Nexus3-related plugin configurations
    Affected if Nexus3ChoiceListProvider is configured with stored credentials
  6. Review stored credentials that could be targeted
    Navigate to Jenkins > Manage Jenkins > Manage Credentials and review any credentials associated with Artifactory, Nexus, or Nexus3 service URLs. Note the credentials IDs as the vulnerability requires knowledge of a specific credentials ID to exploit
    Affected if Credentials with IDs corresponding to Artifactory/Nexus/Nexus3 integrations exist in Jenkins

The environment is affected if the Maven Artifact ChoiceListProvider plugin version is 1.3.1 or earlier AND any of the affected providers (ArtifactoryChoiceListProvider, NexusChoiceListProvider, or Nexus3ChoiceListProvider) are configured with stored credentials in Jenkins.

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 1.3.1
Interim mitigation

Upgrade the Maven Artifact ChoiceListProvider plugin to a version newer than 1.3.1. Additionally, review and rotate any credentials that may have been exposed or could be targeted using this vulnerability.

Fix this in Maven Artifact Choicelistprovider \(nexus\) Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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