First published: Tue May 17 2022(Updated: )
Jenkins Mercurial Plugin 2.16 and earlier allows attackers able to configure pipelines to check out some SCM repositories stored on the Jenkins controller's file system using local paths as SCM URLs, obtaining limited information about other projects' SCM contents.
Credit: jenkinsci-cert@googlegroups.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/jenkins | <2-plugins-0:4.8.1672842762-1.el8 | 2-plugins-0:4.8.1672842762-1.el8 |
redhat/Mercurial Plugin | <2.16.1 | 2.16.1 |
Mercurial | <2.16.1 | |
Jenkins | <=4.11.1 | |
Mercurial | <=2.16 | |
Jenkins Repository Connector | <=1.14.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-30948 is considered a medium severity vulnerability due to the potential exposure of sensitive information.
To mitigate CVE-2022-30948, update the Jenkins Mercurial Plugin to version 2.17 or later.
CVE-2022-30948 affects Jenkins Mercurial Plugin versions 2.16 and earlier.
CVE-2022-30948 exploits the ability for attackers to configure pipelines to access restricted SCM repository paths on the Jenkins controller.
Yes, CVE-2022-30948 can lead to unauthorized access to limited information about other projects' SCM contents through insecure configuration.