CVE-2022-28148 json
Path traversal vulnerability on Windows in Jenkins Continuous Integration with Toad Edge Plugin
published 4y ago modified 4mo ago also GHSA-mc92-c859-jr66 , EUVD-2022-1474
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 79%
- public exploits
- 0
- none known
Summary
The file browser in Jenkins Continuous Integration with Toad Edge Plugin 2.3 and earlier may interpret some paths to files as absolute on Windows, resulting in a path traversal vulnerability allowing attackers with Item/Read permission to obtain the contents of arbitrary files on Windows controllers.
Patch / fix
- maven org.jenkins-ci.plugins:ci-with-toad-edge 2.4
Is CVE-2022-28148 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
1.84% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/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 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:ci-with-toad-edge | <2.4 |
2.4 |
Affected products
- Jenkins project Jenkins Continuous Integration with Toad Edge Plugin
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
jenkins.io
/security/advisory/2022-03-29/#SECURITY-2654
web, vendor-advisory
-
openwall.com
/lists/oss-security/2022/03/29/1
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-28148
advisory
-
github.com
/jenkinsci/ci-with-toad-edge-plugin
package
Sources
- CVE List CVE-2022-28148
- GitHub Advisory GHSA-mc92-c859-jr66
- NVD CVE-2022-28148
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.