Skip to content
Fencer Intel
high 7.5

CVE-2014-2828 json

OpenStack Identity (Keystone) DoS through V3 API authentication chaining

published 2014-04-15 12 y ago modified 2026-06-17 4 mo ago also GHSA-6mv3-p2gr-wgqf , PYSEC-2014-106 , EUVD-2014-0026

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

Summary

The V3 API in OpenStack Identity (Keystone) 2013.1 before 2013.2.4 and icehouse before icehouse-rc2 allows remote attackers to cause a denial of service (CPU consumption) via a large number of the same authentication method in a request, aka "authentication chaining."

Patch / fix

  • pypi keystone 8.0.0a0
  • keystone Debian 14, Debian 13, Debian 12 2014.1-1

debian advisories DEBIAN-CVE-2014-2828

  • openstack-keystone openstack 4 2013.2.4-1.el6ost
  • python-keystone openstack 4 2013.2.4-1.el6ost

red hat advisories RHSA-2014:1688

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-2828 updated cvss 5.0

openstack-keystone: denial of service via V3 API authentication chaining

  • Red Hat OpenStack Platform 3 openstack-keystone
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux OpenStack Platform 4.0 python-keystone 2013.2.4-1.el6ost, openstack-keystone 2013.2.4-1.el6ost
    fixed: vendor fix RHSA-2014:1688

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

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

CVSS scores

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

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.