CVE-2022-38664 json
Cross-site Scripting in Jenkins Job Configuration History Plugin
published 4y ago modified 4mo ago also GHSA-28w4-h56g-grg7 , EUVD-2022-6457
- cvss
- 5.4
- 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 55%
- public exploits
- 0
- none known
Summary
Jenkins Job Configuration History Plugin 1165.v8cc9fd1f4597 and earlier does not escape the job name on the System Configuration History page, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to configure job names.
Patch / fix
- maven org.jenkins-ci.plugins:jobConfigHistory 1166.vc9f255f45b
Is CVE-2022-38664 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.75% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| GitHub | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:jobConfigHistory | <1166.vc9f255f45b |
1166.vc9f255f45b |
Affected products
- Jenkins project Jenkins Job Configuration History Plugin
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/jenkinsci/job-config-history-plugin/commit/c9f255f45b8a6ed008d66be094526adfd80ca035
web
-
jenkins.io
/security/advisory/2022-08-23/#SECURITY-2765
web, vendor-advisory
-
openwall.com
/lists/oss-security/2022/08/23/2
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-38664
advisory
-
github.com
/jenkinsci/job-config-history-plugin
package
Sources
- CVE List CVE-2022-38664
- GitHub Advisory GHSA-28w4-h56g-grg7
- NVD CVE-2022-38664
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.