CVE-2019-10363 json
Cleartext Transmission of Sensitive Information in Jenkins Configuration as Code Plugin
published 7y ago modified 4mo ago also GHSA-r69h-6c4g-63xf , EUVD-2022-5112
- cvss
- 4.9
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 49%
- public exploits
- 0
- none known
Summary
Jenkins Configuration as Code Plugin 1.24 and earlier did not reliably identify sensitive values expected to be exported in their encrypted form.
Patch / fix
- maven io.jenkins:configuration-as-code 1.25
Is CVE-2019-10363 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.61% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
| GitHub | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | io.jenkins:configuration-as-code | <1.25 |
1.25 |
Affected products
- Jenkins project Jenkins Configuration as Code Plugin
Classification
References
-
github.com
/jenkinsci/configuration-as-code-plugin/commit/7506d50b846460ec9f4506f0e228d2e44f0d5a3e
web
-
jenkins.io
/security/advisory/2019-07-31/#SECURITY-1458
web, vendor-advisory
-
openwall.com
/lists/oss-security/2019/07/31/1
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-10363
advisory
Sources
- CVE List CVE-2019-10363
- GitHub Advisory GHSA-r69h-6c4g-63xf
- NVD CVE-2019-10363
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.