Skip to content
Fencer Intel
medium 5.3

CVE-2013-1865 json

OpenStack Keystone Improper Authentication vulnerability

published 13y ago modified 4mo ago also GHSA-22q6-wwq7-2jj9 , PYSEC-2013-39 , EUVD-2013-0014

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

Summary

OpenStack Keystone Folsom (2012.2) does not properly perform revocation checks for Keystone PKI tokens when done through a server, which allows remote attackers to bypass intended access restrictions via a revoked PKI token.

Patch / fix

  • pypi keystone 2012.2.4
  • openstack-keystone openstack 2 2012.2.3-7.el6ost
  • python-keystone openstack 2 2012.2.3-7.el6ost

red hat advisories RHSA-2013:0708

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

keystone: online validation of Keystone PKI tokens bypasses revocation check

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

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
pypi keystone
>=2012.2, <2012.2.4
2012.2.4

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.