First published: Wed Nov 04 2020(Updated: )
A missing permission check in Jenkins Mercurial Plugin 2.11 and earlier allows attackers with Overall/Read permission to obtain a list of names of configured Mercurial installations.
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/jenkins | <2-plugins-0:3.11.1612862361-1.el7 | 2-plugins-0:3.11.1612862361-1.el7 |
redhat/jenkins | <2-plugins-0:4.5.1610108899-1.el7 | 2-plugins-0:4.5.1610108899-1.el7 |
redhat/jenkins | <2-plugins-0:4.6.1609853716-1.el8 | 2-plugins-0:4.6.1609853716-1.el8 |
maven/org.jenkins-ci.plugins:mercurial | <2.8.1 | 2.8.1 |
maven/org.jenkins-ci.plugins:mercurial | =2.9 | 2.9.1 |
maven/org.jenkins-ci.plugins:mercurial | =2.10 | 2.10.1 |
maven/org.jenkins-ci.plugins:mercurial | =2.11 | 2.12 |
redhat/mercurial | <2.12 | 2.12 |
Mercurial | <=2.11 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)
CVE-2020-2306 has a medium severity level as it allows unauthorized access to configured Mercurial installations.
To fix CVE-2020-2306, upgrade the Jenkins Mercurial Plugin to version 2.12 or later.
CVE-2020-2306 affects Jenkins Mercurial Plugin versions 2.11 and earlier.
CVE-2020-2306 enables attackers with overall read permission to retrieve configuration details of Mercurial installations.
No, attackers can exploit CVE-2020-2306 without needing to authenticate, as the vulnerability exists in an HTTP endpoint.