Skip to content
Fencer Intel
medium 5.0

CVE-2013-0282 json

OpenStack Keystone allows context-dependent attackers to bypass access restrictions

published 13y ago modified 4mo ago also GHSA-8833-qrvm-wc3h , PYSEC-2026-652 , EUVD-2022-3144

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

Summary

OpenStack Keystone Grizzly before 2013.1, Folsom 2012.1.3 and earlier, and Essex does not properly check if the (1) user, (2) tenant, or (3) domain is enabled when using EC2-style authentication, which allows context-dependent attackers to bypass access restrictions.

Patch / fix

  • pypi keystone 8.0.0a0
  • keystone Debian 14, Debian 13, Debian 12 2012.1.1-13

debian advisories DEBIAN-CVE-2013-0282

  • openstack-keystone openstack 2 2012.2.3-3.el6ost
  • python-keystone openstack 2 2012.2.3-3.el6ost

red hat advisories RHSA-2013:0596

Is CVE-2013-0282 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-2013-0282 updated cvss 4.0

Keystone: EC2-style authentication accepts disabled user/tenants

  • Red Hat OpenStack Folsom python-keystone 2012.2.3-3.el6ost, openstack-keystone 2012.2.3-3.el6ost
    fixed: vendor fix RHSA-2013:0596

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.76% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected packages

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

Classification

Weakness

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.