CVE-2014-3520
First published: Sun Oct 26 2014(Updated: )
OpenStack Identity (Keystone) before 2013.2.4, 2014.x before 2014.1.2, and Juno before Juno-2 allows remote authenticated trustees to gain access to an unauthorized project for which the trustor has certain roles via the project ID in a V2 API trust token request.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| OpenStack keystonemiddleware | >=2013.2<2013.2.4 | |
| OpenStack keystonemiddleware | >=2014.1<2014.1.2 |
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-2014-3520?
CVE-2014-3520 is classified as a moderate severity vulnerability.
How do I fix CVE-2014-3520?
To fix CVE-2014-3520, upgrade OpenStack Keystone to version 2013.2.4 or 2014.1.2 and later.
Who is affected by CVE-2014-3520?
CVE-2014-3520 affects remote authenticated users of OpenStack Identity (Keystone) versions prior to 2013.2.4 and 2014.1.2.
What types of attacks can CVE-2014-3520 facilitate?
CVE-2014-3520 can potentially allow unauthorized access to projects via the misuse of trust tokens.
What is the impact of CVE-2014-3520 on OpenStack installations?
CVE-2014-3520 can lead to data exposure and unauthorized actions in projects for which the trustor has roles.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/remedy
- agent/last-modified-date
- agent/severity
- agent/references
- agent/author
- agent/description
- agent/event
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/openstack
- canonical/openstack keystonemiddleware
- version/openstack keystonemiddleware/2013.2
- version/openstack keystonemiddleware/2014.1