Skip to content
Fencer Intel
high 7.5

CVE-2015-7546 json

OpenStack Identity Keystone and keystonemiddleware Insufficiently Protected Credentials

published 2016-02-03 10 y ago modified 2026-07-13 3 mo ago also GHSA-8c4w-v65p-jvcv , PYSEC-2016-20 , PYSEC-2026-2549 , EUVD-2016-0013

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.0%
EPSS 2.0% chance of exploitation in 30 days, percentile 80%
public exploits
0
none known

Summary

The identity service in OpenStack Identity (Keystone) before 2015.1.3 (Kilo) and 8.0.x before 8.0.2 (Liberty) and keystonemiddleware (formerly python-keystoneclient) before 1.5.4 (Kilo) and Liberty before 2.3.3 does not properly invalidate authorization tokens when using the PKI or PKIZ token providers, which allows remote authenticated users to bypass intended access restrictions and gain access to cloud resources by manipulating byte fields within a revoked token.

Patch / fix

  • pypi keystone 8.1.0, 9.0.0.0b2
  • pypi keystonemiddleware 1.5.4, 2.3.3, 4.1.0
  • openstack keystone 8.0.2
  • keystone Debian 14, Debian 13, Debian 12 2:9.0.0~rc2-1
  • python-keystonemiddleware Debian 14, Debian 13, Debian 12 3.0.0-1

debian advisories DEBIAN-CVE-2015-7546

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-7546 updated cvss 5.8

openstack-keystone: Improper check of tampered revocated PKI/PKIZ token

  • Red Hat Enterprise Linux OpenStack Platform 5 (Icehouse) openstack-keystone Red Hat Enterprise Linux OpenStack Platform 6 (Juno) openstack-keystone Red Hat Enterprise Linux OpenStack Platform 7 (Kilo) python-keystone, openstack-keystone Red Hat OpenStack Platform 8 (Liberty) python-keystone, openstack-keystone
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.00% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.0 AV:N/AC:M/Au:S/C:P/I:P/A:P
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi keystone
>=9.0.0.0b1, <9.0.0.0b2
>=8.0, <8.1.0
9.0.0.0b2
8.1.0
pypi keystonemiddleware
>=2.4.0, <4.1.0
<1.5.4
>=1.6.0, <2.3.3
4.1.0
1.5.4
2.3.3

Classification

Weakness
  • CWE-522 Insufficiently Protected Credentials

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.