Skip to content
Fencer Vulns
high 8.8

CVE-2019-19687 json

OpenStack Keystone Credential Leakage

published 2019-12-09 6 y ago modified 2026-06-17 4 mo ago also GHSA-2j23-fwqm-mgwr , PYSEC-2019-29 , EUVD-2019-0072

cvss
8.8
version 3.1, 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 15.0.0 and 16.0.0 is affected by Data Leakage in the list credentials API. Any user with a role on a project is able to list any credentials with the /v3/credentials API when enforce_scope is false. Users with a role on a project are able to view any other users' credentials, which could (for example) leak sign-on information for Time-based One Time Passwords (TOTP). Deployments with enforce_scope set to false are affected. (There will be a slight performance impact for the list credentials API once this issue is fixed.)

Patch / fix

  • pypi keystone 15.0.1, 16.0.1
  • keystone Debian 14, Debian 13, Debian 12 2:16.0.0-5

debian advisories DEBIAN-CVE-2019-19687

  • python3-mistral openstack 16 9.0.2-0.20191125120837.6651519.el8ost
  • python3-keystone openstack 16 1:16.0.1-0.20191210095025.bd3f637.el8ost
  • openstack-mistral openstack 16 9.0.2-0.20191125120837.6651519.el8ost
  • openstack-keystone openstack 16 1:16.0.1-0.20191210095025.bd3f637.el8ost
  • openstack-mistral-all openstack 16 9.0.2-0.20191125120837.6651519.el8ost
  • openstack-mistral-api openstack 16 9.0.2-0.20191125120837.6651519.el8ost
  • openstack-mistral-common openstack 16 9.0.2-0.20191125120837.6651519.el8ost
  • openstack-mistral-engine openstack 16 9.0.2-0.20191125120837.6651519.el8ost

red hat advisories RHEA-2020:0283RHSA-2019:4358

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-2019-19687 updated cvss 8.1

openstack-keystone: Credentials API allows non-admin to list and retrieve all users credentials

  • Red Hat OpenStack Platform 15.0 python3-keystone 15.0.1-0.20190720060412.5f27c4b.1.el8ost, openstack-keystone 15.0.1-0.20190720060412.5f27c4b.1.el8ost
    fixed: vendor fix “To mitigate this issue, set the [oslo_policy] enforce_scope option to 'true' in the keystone.conf file.” RHSA-2019:4358
  • Red Hat OpenStack Platform 16.0 python3-keystone 16.0.1-0.20191210095025.bd3f637.el8ost, openstack-keystone 16.0.1-0.20191210095025.bd3f637.el8ost
    fixed: vendor fix “To mitigate this issue, set the [oslo_policy] enforce_scope option to 'true' in the keystone.conf file.” RHEA-2020:0283
  • Red Hat JBoss Fuse 6 jclouds_openstack-keystone_api jclouds_openstack-keystone_api Red Hat OpenStack 16 Cinderlib future 0.16.0-6.el8ost, subunit 1.3.0-7.el8ost, numpy 1.15.1-2.2.el8ost, pyparsing 2.3.1-1.el8ost, python-ddt 1.0.1-4.el8ost, python-pbr 5.1.2-2.el8ost, +232 more Red Hat OpenStack Platform 16.0 zstd 1.3.4-2.el8ost, crudini 0.9-6.el8ost, etcd 3.2.21-2.el8ost, hdf5 1.8.20-7.el8ost, hiera 3.3.1-5.el8ost, novnc 1.1.0-1.el8ost, +1103 more
    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.78% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
pypi keystone
>=15.0.0, <15.0.1
>=16.0.0, <16.0.1
<16.0.1
15.0.1
16.0.1

Classification

Weakness
  • CWE-522 Insufficiently Protected Credentials

References

Sources

Fencer Vulns 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.