CVE-2019-10367 json
Insertion of Sensitive Information into Log File in Jenkins Configuration as Code Plugin
published 7y ago modified 4mo ago also GHSA-7c3v-vc3x-x789 , EUVD-2022-2971
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
Due to an incomplete fix of CVE-2019-10343, Jenkins Configuration as Code Plugin 1.26 and earlier did not properly apply masking to some values expected to be hidden when logging the configuration being applied.
Patch / fix
- maven io.jenkins:configuration-as-code 1.27
Is CVE-2019-10367 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.38% chance of exploitation in the next 30 days, higher than 32% 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.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | io.jenkins:configuration-as-code | <1.27 |
1.27 |
Affected products
- Jenkins project Jenkins Configuration as Code Plugin
Classification
- Weakness
-
- CWE-532 Insertion of Sensitive Information into Log File
References
-
github.com
/jenkinsci/configuration-as-code-plugin/commit/322ef83f3200ce6076129c014209ef938e556774
web
-
jenkins.io
/security/advisory/2019-08-07/#SECURITY-1497
web, vendor-advisory
-
openwall.com
/lists/oss-security/2019/08/07/1
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-10367
advisory
-
jenkins.io
/security/advisory/2019-07-31/#SECURITY-1279
web
Sources
- CVE List CVE-2019-10367
- GitHub Advisory GHSA-7c3v-vc3x-x789
- NVD CVE-2019-10367
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.