CVE-2018-1999001
CVE-2018-1999001 is a high-severity vulnerability in Jenkins with a CVSS 3.x base score of 8.8. Its EPSS exploit-prediction score of 18% places it in the 97th percentile, indicating an elevated likelihood of exploitation.
Key facts
- Severity: High (CVSS 3.x base score 8.8)
- CVSS v2: 4.3
- EPSS exploit prediction: 18% (97th percentile)
- Actively exploited: Not listed in CISA KEV
- Affected product: Jenkins
- Published:
- Last modified:
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.
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 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2018-1999001 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 18% (97th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2018-1999001?
- CVE-2018-1999001 primarily affects Jenkins. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
- How do I fix CVE-2018-1999001?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2018-1999001 published?
- CVE-2018-1999001 was published on 2018-07-23 and last updated on 2026-06-17.
References
- https://jenkins.io/security/advisory/2018-07-18/#SECURITY-897
- https://www.oracle.com/security-alerts/cpuapr2022.html
Affected products (2)
- cpe:2.3:a:jenkins:jenkins:*:*:*:*:*:*:*:*
- cpe:2.3:a:oracle:communications_cloud_native_core_automated_test_suite:1.9.0:*:*:*:*:*:*:*
More vulnerabilities in Jenkins
- CVE-2024-23897 — Critical (CVSS 9.8): Jenkins 2.441 and earlier, LTS 2.426.2 and earlier does not disable a feature of its CLI command parser that replaces…
- CVE-2021-21696 — Critical (CVSS 9.8): Jenkins 2.318 and earlier, LTS 2.303.2 and earlier does not limit agent read/write access to the libs/ directory inside…
- CVE-2021-21694 — Critical (CVSS 9.8): FilePath#toURI, FilePath#hasSymlink, FilePath#absolutize, FilePath#isDescendant, and FilePath#get*DiskSpace do not…
- CVE-2021-21693 — Critical (CVSS 9.8): When creating temporary files, agent-to-controller access to create those files is only checked after they've been…
- CVE-2021-21692 — Critical (CVSS 9.8): FilePath#renameTo and FilePath#moveAllChildrenTo in Jenkins 2.318 and earlier, LTS 2.303.2 and earlier only check…
- CVE-2021-21691 — Critical (CVSS 9.8): Creating symbolic links is possible without the 'symlink' agent-to-controller access control permission in Jenkins…