CVE-2017-2673: An authorization-check flaw was discovered in federation configurations of the OpenStack Identity service (keystone).
Noroxi assessment
Priority: Monitor (action score 29/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: 2.3% (FIRST EPSS); higher than 83.5% of all records.
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: keystone (Debian:12) 2:10.0.0-9; keystone (PyPI) 10.0.2, 11.0.1; openstack-keystone (Red Hat:openstack:10::el7) 1:10.0.1-3.el7ost.
Low priority for now. Upgrade to keystone (Debian:12) 2:10.0.0-9; keystone (PyPI) 10.0.2, 11.0.1; openstack-keystone (Red Hat:openstack:10::el7) 1:10.0.1-3.el7ost 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
An authorization-check flaw was discovered in federation configurations of the OpenStack Identity service (keystone). An authenticated federated user could request permissions to a project and unintentionally be granted all related roles including administrative roles.
- Published
- Jul 19, 2018
- Updated
- Jun 16, 2026
- EPSS
- 2.3% · 83th percentile
- CWE
- CWE-863
Report tools
Action score
29
Low priority for now.
- CVSS
- 28 / 40 · 7.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.3%
CNA vs NVD score
- NVD
- 7.2
- CNA · redhat
- 6.8
- 0.4 point gap
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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 |
|---|---|---|
| redhat | openstack | cpe:2.3:a:redhat:openstack |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
[UNKNOWN] openstack-keystone
- n/aaffected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redhat openstack10
- redhat openstack9
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 2:10.0.0-9 | 2:10.0.0-9 |
| PyPI | keystone | from 10.0.0 · before 10.0.2 | 10.0.2 |
| PyPI | keystone | from 11.0.0 · before 11.0.1 | 11.0.1 |
| PyPI | keystone | from 9.0.0 · before 10.0.2 | 10.0.2 |
| PyPI | keystone | from 9.0.0 · up to and including 9.3.0 | — |
| Red Hat:openstack:10::el7 | openstack-keystone | before 1:10.0.1-3.el7ost | 1:10.0.1-3.el7ost |
| Red Hat:openstack:10::el7 | python-keystone | before 1:10.0.1-3.el7ost | 1:10.0.1-3.el7ost |
| Red Hat:openstack:10::el7 | python-keystone-tests | before 1:10.0.1-3.el7ost | 1:10.0.1-3.el7ost |
| Red Hat:openstack:9::el7 | openstack-keystone | before 1:9.3.0-2.el7ost | 1:9.3.0-2.el7ost |
| Red Hat:openstack:9::el7 | python-keystone | before 1:9.3.0-2.el7ost | 1:9.3.0-2.el7ost |
| Red Hat:openstack:9::el7 | python-keystone-tests | before 1:9.3.0-2.el7ost | 1:9.3.0-2.el7ost |
Same product
redhat: all recordsOther highest-scoring records for the same primary product.
- CVE-2015-1842The puppet manifests in the Red Hat openstack-puppet-modules package before 2014.2.13-2 uses a default password of CHANGEME for the pcsd…42Plan
- CVE-2017-2637A design flaw issue was found in the Red Hat OpenStack Platform director use of TripleO to enable libvirtd based live-migration.41Plan
- CVE-2013-2121Eval injection vulnerability in the create method in the Bookmarks controller in Foreman before 1.2.0-RC2 allows remote authenticated users…40Plan
Published before and after this one in the same product
- ← EarlierCVE-2016-4474Jun 30, 2016 · The image build process for the overcloud images in Red Hat OpenStack Platform 8.0 (Liberty) director and Red Hat Enterprise Linux…35Monitor
- ← EarlierCVE-2016-4985Jul 12, 2016 · The ironic-api service in OpenStack Ironic before 4.2.5 (Liberty) and 5.x before 5.1.2 (Mitaka) allows remote attackers to obtain sensitive…31Monitor
- Later →CVE-2017-2622Jul 27, 2018 · An accessibility flaw was found in the OpenStack Workflow (mistral) service where a service log directory was improperly made world…22Monitor
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 | 2:10.0.0-9 · Debian:12 | Package registry (OSV) |
| PyPI:keystone | 10.0.2 | Package registry (OSV) |
| PyPI:keystone | 11.0.1 | Package registry (OSV) |
| red hat:openstack-keystone | 1:9.3.0-2.el7ost · Red Hat:openstack:9::el7 | Package registry (OSV) |
| red hat:python-keystone | 1:9.3.0-2.el7ost · Red Hat:openstack:9::el7 | Package registry (OSV) |
| red hat:python-keystone-tests | 1:9.3.0-2.el7ost · Red Hat:openstack:9::el7 | 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
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.