Skip to content
Fencer Intel
medium 4.0

CVE-2013-0212 json

OpenStack Glance logs user name and password in cleartext

published 13y ago modified 4mo ago also GHSA-xv7j-2v4w-cjvh , PYSEC-2013-37 , EUVD-2013-0043

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

Summary

store/swift.py in OpenStack Glance Essex (2012.1), Folsom (2012.2) before 2012.2.3, and Grizzly, when in Swift single tenant mode, logs the Swift endpoint's user name and password in cleartext when the endpoint is misconfigured or unusable, allows remote authenticated users to obtain sensitive information by reading the error messages.

Patch / fix

  • pypi glance 2012.2.3
  • glance Debian 14, Debian 13, Debian 12 2012.1.1-4

debian advisories DEBIAN-CVE-2013-0212

  • openstack-glance openstack 2 2012.2.1-4.el6ost
  • python-glance openstack 2 2012.2.1-4.el6ost

red hat advisories RHSA-2013:0209

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

openstack-glance: Backend password leak in Glance error message

  • Red Hat OpenStack Folsom python-glance 2012.2.1-4.el6ost, openstack-glance 2012.2.1-4.el6ost
    fixed: vendor fix RHSA-2013:0209

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
pypi glance
>=2012.1, <2012.2.3
2012.2.3

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

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.