dbcve.org
Job ImportApplication · Jenkins

CVE-2019-1003016

HIGH · 8.8 CVSS v3.0 Published 2019-02-06
Fix available
A fix is available. Upgrade to after 2.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Job Import Plugin 2.1 and earlier in src/main/java/org/jenkins/ci/plugins/jobimport/JobImportAction.java, src/main/java/org/jenkins/ci/plugins/jobimport/JobImportGlobalConfig.java, src/main/java/org/jenkins/ci/plugins/jobimport/model/JenkinsSite.java that allows attackers with Overall/Read permission to have Jenkins connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials 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 · high confidence

The Jenkins Job Import Plugin versions 2.1 and earlier contains an exposure of sensitive information vulnerability in JobImportAction.java, JobImportGlobalConfig.java, and JenkinsSite.java. Attackers with Overall/Read permission (the lowest privilege level) can configure Jenkins to connect to attacker-controlled URLs using attacker-specified credential IDs, enabling exfiltration of stored credentials from the Jenkins credential store.

MitigationUpgrade Jenkins Job Import Plugin to version newer than 2.1. Review credential usage logs and rotate any credentials that may have been accessed through 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
Job ImportApplication
Affected:<= 2.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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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. Identify if Jenkins Job Import Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Job Import' or list all installed plugins via Jenkins script console: Jenkins.instance.pluginManager.plugins.each { if (it.shortName.contains('job-import')) println it.displayName + ' ' + it.version }
    Affected if The plugin is listed as installed with a version of 2.1 or earlier
  2. Verify the plugin version against affected range
    In Manage Jenkins > Manage Plugins > Installed, confirm the version number of the Job Import Plugin. If using the script console, the output will show the version directly
    Affected if Version is 2.1 or any version lower than 2.1 (e.g., 2.0, 1.x)
  3. Confirm plugin job import functionality was used
    Check Jenkins job configuration pages or build logs for any jobs that used the Job Import Plugin feature, or review JobImportAction/JobImportGlobalConfig configuration in Jenkins system configuration
    Affected if The plugin was configured or used to import jobs from external Jenkins instances
  4. Review credential usage logs for the plugin
    Navigate to Manage Jenkins > System Log > All Jenkins Logs and search for entries containing 'JobImport' or credential usage from the Job Import Plugin. Alternatively, check audit logs if enabled
    Affected if Logs show the plugin accessing credentials, especially to external/unexpected URLs

A user is affected if the Jenkins Job Import Plugin version 2.1 or earlier is installed and the plugin has been used to import jobs, allowing any user with Overall/Read permission to potentially exfiltrate credentials.

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

Upgrade Jenkins Job Import Plugin to version newer than 2.1. Review credential usage logs and rotate any credentials that may have been accessed through this vulnerability.

Fix this in Job Import Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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