First published: Wed Jan 12 2022(Updated: )
Jenkins Warnings Next Generation Plugin 9.10.2 and earlier does not restrict the name of a file when configuring custom ID, allowing attackers with Item/Configure permission to write and read specific files with a hard-coded suffix on the Jenkins controller file system.
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
Affected Software | Affected Version | How to fix |
---|---|---|
maven/io.jenkins.plugins:warnings-ng | <9.0.2 | 9.0.2 |
maven/io.jenkins.plugins:warnings-ng | >=9.1.0<9.5.2 | 9.5.2 |
maven/io.jenkins.plugins:warnings-ng | >=9.6.0<9.7.1 | 9.7.1 |
maven/io.jenkins.plugins:warnings-ng | >=9.8.0<9.10.3 | 9.10.3 |
Jenkins Warnings | >=9.0.0<9.0.2 | |
Jenkins Warnings | >=9.5.0<9.5.2 | |
Jenkins Warnings | >=9.10.0<=9.10.2 | |
Jenkins Warnings | =9.7.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-23107 has a medium severity level due to its potential to allow unauthorized file access on the Jenkins controller.
To fix CVE-2022-23107, upgrade the Jenkins Warnings Next Generation Plugin to version 9.10.3 or later.
Versions 9.0.0 up to 9.10.2 of the Jenkins Warnings Next Generation Plugin are affected by CVE-2022-23107.
If CVE-2022-23107 is exploited, attackers can read and write specific files on the Jenkins controller's file system.
Yes, an attacker needs Item/Configure permission to exploit CVE-2022-23107.