Jenkins Code Coverage API Plugin 1.1.2 and earlier does not escape the filename of the coverage report used in its view, resulting in a stored XSS vulnerability exploitable by users able to change job configurations.
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Link | Tags |
---|---|
https://jenkins.io/security/advisory/2020-01-29/#SECURITY-1680 | vendor advisory |
http://www.openwall.com/lists/oss-security/2020/01/29/1 | third party advisory mailing list |