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...
Product
jenkins continuous integration with toad edge vulnerabilities
4 published CVES affecting jenkins continuous integration with toad edge, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 4
- Critical
- 0
- High
- 0
- Medium
- 4
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest jenkins continuous integration with toad edge CVEs
Newest publication first
-
MediumCVSS 6.5 EPSS 1.8%
-
CVE-2022-28147 Missing permission check in Jenkins Continuous Integration with Toad Edge Plugin
PublishedMediumCVSS 4.3 EPSS 0.75%A missing permission check in Jenkins Continuous Integration with Toad Edge Plugin 2.3 and earlier allows attackers with Overall/Read permission to check for the existence of an attacker-specified file path on the Jenkins controller file system.
-
MediumCVSS 6.5 EPSS 1.8%
Jenkins Continuous Integration with Toad Edge Plugin 2.3 and earlier allows attackers with Item/Configure permission to read arbitrary files on the Jenkins controller by specifying an input folder on the Jenkins controller as a parameter to its build steps.
-
MediumCVSS 5.4 EPSS 0.82%
Jenkins Continuous Integration with Toad Edge Plugin 2.3 and earlier does not apply Content-Security-Policy headers to report files it serves, resulting in a stored cross-site scripting (XSS) exploitable by attackers with Item/Configure permission or otherwise able to control rep...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.