CVE-2019-10449 json
Jenkins Fortify on Demand Plugin stores credentials in plain text
published 7y ago modified 4mo ago also GHSA-hhhh-69qp-5p2v , EUVD-2022-4156
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 58%
- public exploits
- 0
- none known
Summary
Jenkins Fortify on Demand Plugin stores credentials unencrypted in job config.xml files on the Jenkins master where they can be viewed by users with Extended Read permission, or access to the master file system.
Patch / fix
- maven org.jenkins-ci.plugins:fortify-on-demand-uploader 5.0.0
Is CVE-2019-10449 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
0.85% chance of exploitation in the next 30 days, higher than 58% 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 | 4.3 | CVSS:3.0/AV:N/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:fortify-on-demand-uploader | <5.0.0 |
5.0.0 |
Affected products
- Jenkins project Jenkins Fortify on Demand Plugin
Classification
- Weakness
-
- CWE-312 Cleartext Storage of Sensitive Information
References
-
github.com
/jenkinsci/fortify-on-demand-uploader-plugin/commit/277642040362bcc64df163bfc1ab48f7763c2853
web
-
github.com
/jenkinsci/fortify-on-demand-uploader-plugin/commit/83b23662dc0ce9486b904e282bd8047496730819
web
-
jenkins.io
/security/advisory/2019-10-16/#SECURITY-1433
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-10449
advisory
-
github.com
/jenkinsci/fortify-on-demand-uploader-plugin
package
Sources
- CVE List CVE-2019-10449
- GitHub Advisory GHSA-hhhh-69qp-5p2v
- NVD CVE-2019-10449
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.