First published: Mon Jul 23 2018(Updated: )
A unauthorized modification of configuration vulnerability exists in Jenkins 2.132 and earlier, 2.121.1 and earlier in User.java that allows attackers to provide crafted login credentials that cause Jenkins to move the config.xml file from the Jenkins home directory. If Jenkins is started without this file present, it will revert to the legacy defaults of granting administrator access to anonymous users.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.jenkins-ci.main:jenkins-core | >=2.122<2.132 | 2.132 |
maven/org.jenkins-ci.main:jenkins-core | <2.121.2 | 2.121.2 |
Jenkins | <=2.121.1 | |
Jenkins | >=2.122<=2.132 | |
Oracle Communications Cloud Native Core Automated Test Suite | =1.9.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2018-1999001 has been assigned a medium severity rating due to its potential to allow unauthorized modification of configuration files in Jenkins.
To fix CVE-2018-1999001, upgrade Jenkins to version 2.132 or higher, or to 2.121.2.
Jenkins versions 2.132 and earlier, as well as 2.121.1 and earlier, are affected by CVE-2018-1999001.
CVE-2018-1999001 is classified as an unauthorized modification of configuration vulnerability.
Yes, CVE-2018-1999001 could potentially lead to data loss by allowing attackers to manipulate the config.xml file.