Vulnerabilities · 2015 · Jenkins
CVE-2015-1814
Jenkins vulnerability
The API token-issuing service in Jenkins before 1.606 and LTS before 1.596.2 allows remote attackers to gain privileges via a "forced API token change" involving anonymous users.
Affected products
Jenkins, Openshift. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Jenkins runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-03-23 · Vendor Advisory
- rhn.redhat.com/errata/RHSA-2015-1844.html
- access.redhat.com/errata/RHSA-2016:0070
- bugzilla.redhat.com/show_bug.cgi?id=1205616
- nvd.nist.gov/vuln/detail/CVE-2015-1814
- github.com/jenkinsci/jenkins/commit/57e78880cc035874bda916ef4d8d7fd7642af9db
- github.com/advisories/GHSA-3269-jqp5-v8c9
- nvd.nist.gov/vuln/detail/CVE-2015-1814
- cve.org/CVERecord?id=CVE-2015-1814
More vulnerabilities in Jenkins products
CVE-2025-67643CVE-2025-67642CVE-2025-67641CVE-2025-67640CVE-2025-67639CVE-2025-67638CVE-2025-67637CVE-2025-67636All 1,739
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.