CVE-2019-10398 json
Jenkins Beaker Builder Plugin has Insufficiently Protected Credentials
published 7y ago modified 4mo ago also GHSA-9678-5f6f-wp3f , EUVD-2022-3300
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 21%
- public exploits
- 0
- none known
Summary
Jenkins Beaker Builder Plugin 1.9 and earlier stored credentials unencrypted in its global configuration file on the Jenkins master where they could be viewed by users with access to the master file system.
Patch / fix
- maven org.jenkins-ci.plugins:beaker-builder 1.10
Is CVE-2019-10398 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.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/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:beaker-builder | <1.10 |
1.10 |
Affected products
- Jenkins project Jenkins Beaker Builder Plugin
Classification
- Weakness
-
- CWE-522 Insufficiently Protected Credentials
References
-
github.com
/jenkinsci/beaker-builder-plugin/commit/be0101f3541a5d2c28cf226c8b2e55cd4cfc94da
web
-
jenkins.io
/security/advisory/2019-09-12/#SECURITY-1545
web, vendor-advisory
-
openwall.com
/lists/oss-security/2019/09/12/2
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-10398
advisory
Sources
- CVE List CVE-2019-10398
- GitHub Advisory GHSA-9678-5f6f-wp3f
- NVD CVE-2019-10398
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.