OpenStack: Keystone extension of token validity through token chaining
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| OpenStack Folsom for RHEL 6 | |||
| openstack-keystone-0:2012.2.1-1.el6ost | cpe:/a:redhat:openstack:2::el6 | RHSA-2012:1557 | 2012-12-10T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2012-0014 | OpenStack Keystone, as used in OpenStack Folsom 2012.2, does not properly implement token expiration, which allows remote authenticated users to bypass intended authorization restrictions by creating new tokens through token chaining. NOTE: this issue exists because of a CVE-2012-3426 regression. |
Github GHSA |
GHSA-w66p-78g4-mr7g | OpenStack Keystone Insufficient token expiration |
Ubuntu USN |
USN-1641-1 | OpenStack Keystone vulnerabilities |
No CVSS v4.0
No CVSS v3.1
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 2.9% (2.919% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.