CVE-2015-1814

Description

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.

Category

7.5
CVSS
Severity: High
CVSS 2.0 •
EPSS 0.22%
Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory jenkins-ci.org
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://bugzilla.redhat.com/show_bug.cgi?id=1205616
https://access.redhat.com/errata/RHSA-2016:0070 vendor advisory
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-03-23 vendor advisory
http://rhn.redhat.com/errata/RHSA-2015-1844.html vendor advisory

Frequently Asked Questions

What is the severity of CVE-2015-1814?
CVE-2015-1814 has been scored as a high severity vulnerability.
How to fix CVE-2015-1814?
To fix CVE-2015-1814, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2015-1814 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2015-1814 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.