CVE-2022-45401 json
Jenkins Associated Files Plugin vulnerable to cross-site scripting (XSS)
published 3y ago modified 4mo ago also GHSA-chcg-gh9p-96c5 , EUVD-2022-7311
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 52%
- public exploits
- 0
- none known
Summary
Jenkins Associated Files Plugin 0.2.1 and earlier does not escape names of associated files, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.
Is CVE-2022-45401 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.67% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| CNA | 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 | 8.0 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.main:associated-files-plugin | <=0.2.1 |
no fix listed |
Affected products
- Jenkins project Jenkins Associated Files Plugin
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
jenkins.io
/security/advisory/2022-11-15/#SECURITY-2947
web, vendor-advisory
-
openwall.com
/lists/oss-security/2022/11/15/4
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-45401
advisory
-
github.com
/jenkinsci/associated-files-plugin
package
Sources
- CVE List CVE-2022-45401
- GitHub Advisory GHSA-chcg-gh9p-96c5
- NVD CVE-2022-45401
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.