CVE-2019-1003070 json
Jenkins veracode-scanner Plugin stores credentials in plain text
published 7y ago modified 4mo ago also GHSA-5722-v5wc-x7h8 , EUVD-2022-2516
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2019-1003070 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.35% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
| GitHub | 3.0 | 3.3 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:veracode-scanner | <=1.6 |
no fix listed |
Affected products
- Jenkins project Jenkins veracode-scanner Plugin
Classification
- Weakness
-
- CWE-311 Missing Encryption of Sensitive Data
References
-
jenkins.io
/security/advisory/2019-04-03/#SECURITY-952
web, vendor-advisory
-
securityfocus.com
/bid/107790
vdb-entry, third-party-advisory
-
openwall.com
/lists/oss-security/2019/04/12/2
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-1003070
advisory
Sources
- CVE List CVE-2019-1003070
- GitHub Advisory GHSA-5722-v5wc-x7h8
- NVD CVE-2019-1003070
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.