CVE-2018-1999001

HIGHCVSS 8.8/10EPSS 18.12%

Last modified

CVE-2018-1999001 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. 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.. EPSS estimates a 18.12% chance of exploitation in the next 30 days.

Description

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.

Metrics

CVSS 3.1
8.8/10

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS Probability
18.12%

96.8th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

VendorProductVersions
JenkinsJenkins<= 2.121.1
JenkinsJenkins>= 2.122, <= 2.132
OracleCommunications Cloud Native Core Automated Test Suite1.9.0

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2018-1999001?
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.
How severe is CVE-2018-1999001?
CVE-2018-1999001 has a CVSS score of 8.8/10 (HIGH severity). The EPSS model estimates a 18.12% probability of exploitation in the next 30 days.
How do I fix CVE-2018-1999001?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2018-1999001?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST