CVE-2015-1814
First published: Wed Mar 25 2015(Updated: )
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.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/Jenkins | <1.606 | 1.606 |
| redhat/Jenkins | <1.596.2 | 1.596.2 |
| Jenkins LTS | =1.596.1 | |
| Red Hat OpenShift | <=3.1 | |
| Jenkins LTS | <=1.605 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2015-1814?
CVE-2015-1814 is considered a medium severity vulnerability due to its potential to allow unauthorized privilege escalation.
How do I fix CVE-2015-1814?
The recommended fix for CVE-2015-1814 is to upgrade Jenkins to version 1.606 or later, or LTS version 1.596.2 or later.
What systems are affected by CVE-2015-1814?
CVE-2015-1814 affects Jenkins versions prior to 1.606 and LTS versions prior to 1.596.2.
What type of attacks does CVE-2015-1814 allow?
CVE-2015-1814 allows remote attackers to gain privileges through a forced API token change involving anonymous users.
Is there a workaround for CVE-2015-1814?
There are no official workarounds for CVE-2015-1814; upgrading is the only secure solution.
- agent/type
- agent/first-publish-date
- agent/last-modified-date
- agent/references
- agent/weakness
- agent/author
- agent/severity
- agent/description
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2015-1814
- agent/software-canonical-lookup
- agent/event
- agent/source
- agent/tags
- agent/softwarecombine
- collector/nvd-index
- agent/software-canonical-lookup-request
- package-manager/redhat
- vendor/jenkins
- canonical/jenkins lts
- version/jenkins lts/1.596.1
- vendor/redhat
- canonical/red hat openshift
- version/red hat openshift/3.1
- version/jenkins lts/1.605