Skip to content
Fencer Vulns
high 8.8

CVE-2018-1999001 in the critical feed json

Improper Input Validation in Jenkins

published 2018-07-23 8 y ago modified 2026-06-17 4 mo ago also GHSA-j8qv-mj4r-6fw4 , EUVD-2022-4316

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
18.1%
EPSS 18.1% chance of exploitation in 30 days, percentile 97%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.jenkins-ci.main:jenkins-core 2.121.2, 2.132
  • jenkins Arch Linux 2.133-1

arch linux advisories AVG-738

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-1999001 updated cvss 8.8

jenkins: Remote unauthenticated users can move config.xml allowing administrator access to anonymous users

  • Red Hat OpenShift Enterprise 3 jenkins
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

18.12% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N
GitHub 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.main:jenkins-core
<2.121.2
>=2.122, <2.132
2.121.2
2.132

Classification

Weakness
  • CWE-20 Improper Input Validation
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.