Path traversal vulnerability in Jenkins Fortify Plugin
Jenkins Fortify Plugin 20.2.34 and earlier does not sanitize the `appName` and `appVersion` parameters of its Pipeline steps, which are used to write to files inside build directories. This allows attackers with Item/Configure permission to write or overwrite `.xml` files on the Jenkins controller file system with content not controllable by the attacker. Jenkins Fortify Plugin 20.2.35 sanitizes the `appName` and `appVersion` parameters of its Pipeline steps when determining the resulting filename.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2022-25188US | medium4.3 | — | ||
Jenkins Fortify Plugin 20.2.34 and earlier does not sanitize the appName and appVersion parameters of its Pipeline steps, allowing attackers with Item/Configure permission to write… | ||||
references
External citations — patches, advisories, analysis.
- http://www.openwall.com/lists/oss-security/2022/02/15/2WEB
- https://github.com/jenkinsci/fortify-pluginPACKAGE
- https://github.com/jenkinsci/fortify-plugin/commit/ba3030cb63bb86b6bb13342664e0e319f2fee374WEB
- https://nvd.nist.gov/vuln/detail/CVE-2022-25188ADVISORY
- https://www.jenkins.io/security/advisory/2022-02-15/#SECURITY-2214WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan