Skip to content
Fencer Intel
medium 6.5

CVE-2014-0204 json

OpenStack Identity Keystone Improper Privilege Management

published 12y ago modified 4mo ago also GHSA-c4p9-87h3-7vr4 , PYSEC-2026-654 , EUVD-2022-3506

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

Summary

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, which allows remote authenticated users to gain privileges that are assigned to a group with the same ID.

Patch / fix

  • pypi keystone 8.0.0a0
  • openstack keystone 2014.1.1
  • keystone Debian 14, Debian 13, Debian 12 2014.1-5

debian advisories DEBIAN-CVE-2014-0204

Is CVE-2014-0204 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2014-0204 updated cvss 2.7

openstack-keystone: user and group id mismatch

  • Red Hat OpenStack Platform 3 openstack-keystone Red Hat OpenStack Platform 4 openstack-keystone
    not affected: vulnerable code not present

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

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

Exploits and checks

  • bugs.launchpad.net https://bugs.launchpad.net/keystone/+bug/1309228 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P

Affected packages

ecosystem package affected fixed in
pypi keystone
<8.0.0a0
8.0.0a0

Classification

Weakness
  • CWE-269 Improper Privilege Management

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.