dbcve.org
Veracode ScannerApplication · Jenkins

CVE-2019-1003070

HIGH · 8.8 CVSS v3.1 Published 2019-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
Jenkins veracode-scanner Plugin stores credentials unencrypted in its global configuration file on the Jenkins master where they can be viewed by users with access to the master file system.

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 veracode-scanner Plugin stores credentials (likely API keys or tokens for Veracode scanning) in plaintext within its global configuration file on the Jenkins master filesystem. Any user with file system access to the Jenkins master can read these stored credentials without authentication or encryption barriers.

MitigationMigrate credentials storage to use Jenkins' built-in Credentials API, which provides encrypted storage. Existing plaintext credentials should be migrated to the secure credential store, and the plugin should be updated to retrieve credentials through the Credentials binding mechanism rather than reading directly from the configuration file.

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
Veracode ScannerApplication
Affected:all versions

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Check if Veracode Scanner plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Veracode Scanner', or check for the plugin directory at $JENKINS_HOME/plugins/veracode-scanner/
    Affected if The plugin appears in the installed plugins list or the plugin directory exists on the filesystem
  2. Locate the plugin's global configuration file
    Look for the configuration file at $JENKINS_HOME/org.jenkinsci.plugins.veracode_scanner.config.xml or $JENKINS_HOME/jenkins.model.JenkinsLocationConfiguration.xml (the exact path depends on how the plugin stores its config)
    Affected if A configuration XML file associated with the veracode-scanner plugin exists in the Jenkins home directory
  3. Inspect the configuration file for plaintext credentials
    Open the configuration file using a text editor or run: cat $JENKINS_HOME/org.jenkinsci.plugins.veracode_scanner.config.xml (or the located config file path)
    Affected if The file contains readable strings resembling API keys, tokens, passwords, or other credential-like values in plaintext (not base64 encoded, encrypted, or obscured)
  4. Verify credential storage method
    Search the configuration file content for XML elements containing credential data - look for elements like <apiKey>, <token>, <password>, or any field containing a raw alphanumeric string used for authentication to Veracode
    Affected if Credentials are stored in plain XML elements without encryption or Jenkins credential binding references

If the Veracode Scanner plugin is installed and its configuration file contains readable API keys or tokens in plaintext, the environment is affected by this vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Migrate credentials storage to use Jenkins' built-in Credentials API, which provides encrypted storage. Existing plaintext credentials should be migrated to the secure credential store, and the plugin should be updated to retrieve credentials through the Credentials binding mechanism rather than reading directly from the configuration file.

Fix this in Veracode Scanner Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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