CVE-2014-3520: OpenStack Identity (Keystone) before 2013.2.4, 2014.x before 2014.1.2, and Juno before Juno-2 allows remote authenticated trustees to gain…
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.9% (FIRST EPSS); higher than 80% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: keystone (Debian:12) 2014.1.1-3; openstack-keystone (Red Hat:openstack:3::el6) 0:2013.1.5-3.el6ost; openstack-keystone-doc (Red Hat:openstack:3::el6) 0:2013.1.5-3.el6ost.
Low priority for now. Upgrade to keystone (Debian:12) 2014.1.1-3; openstack-keystone (Red Hat:openstack:3::el6) 0:2013.1.5-3.el6ost; openstack-keystone-doc (Red Hat:openstack:3::el6) 0:2013.1.5-3.el6ost or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 26, 2014
- Updated
- Jun 16, 2026
- EPSS
- 1.9% · 80th percentile
- CWE
- CWE-863
Report tools
Action score
27
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.9%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| openstack | keystone | cpe:2.3:a:openstack:keystone |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- openstack keystone2013.2 and later · before 2013.2.4
- openstack keystone2014.1 and later · before 2014.1.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | keystone | before 2014.1.1-3 | 2014.1.1-3 |
| Red Hat:openstack:3::el6 | openstack-keystone | before 0:2013.1.5-3.el6ost | 0:2013.1.5-3.el6ost |
| Red Hat:openstack:3::el6 | openstack-keystone-doc | before 0:2013.1.5-3.el6ost | 0:2013.1.5-3.el6ost |
| Red Hat:openstack:3::el6 | python-keystone | before 0:2013.1.5-3.el6ost | 0:2013.1.5-3.el6ost |
| Red Hat:openstack:4::el6 | openstack-keystone | before 0:2013.2.3-7.el6ost | 0:2013.2.3-7.el6ost |
| Red Hat:openstack:4::el6 | openstack-keystone-doc | before 0:2013.2.3-7.el6ost | 0:2013.2.3-7.el6ost |
| Red Hat:openstack:4::el6 | python-keystone | before 0:2013.2.3-7.el6ost | 0:2013.2.3-7.el6ost |
Same product
openstack: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-12691An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0.36Monitor
- CVE-2020-12690An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0.36Monitor
- CVE-2019-19687OpenStack Keystone 15.0.0 and 16.0.0 is affected by Data Leakage in the list credentials API.36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2014-5253Aug 25, 2014 · OpenStack Identity (Keystone) 2014.1.x before 2014.1.2.1 and Juno before Juno-3 does not properly revoke tokens when a domain is…19Monitor
- ← EarlierCVE-2014-3621Oct 2, 2014 · The catalog url replacement in OpenStack Identity (Keystone) before 2013.2.3 and 2014.1 before 2014.1.2.1 allows remote authenticated users…17Monitor
- Later →CVE-2014-0204Nov 3, 2014 · OpenStack Identity (Keystone) before 2014.1.1 does not properly handle when a role is assigned to a group that has the same ID as a user…26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:keystone | 2014.1.1-3 · Debian:12 | Package registry (OSV) |
| red hat:openstack-keystone | 0:2013.1.5-3.el6ost · Red Hat:openstack:3::el6 | Package registry (OSV) |
| red hat:openstack-keystone-doc | 0:2013.1.5-3.el6ost · Red Hat:openstack:3::el6 | Package registry (OSV) |
| red hat:python-keystone | 0:2013.1.5-3.el6ost · Red Hat:openstack:3::el6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
AV:N/AC:L/Au:S/C:P/I:P/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.