Skip to content
Fencer Intel
low 1.9

CVE-2013-6384 json

(1) impl_db2.py and (2) impl_mongodb.py in OpenStack Ceilometer 2013.2 and earlier, when the logging level is set to INFO, logs the connect…

published 12y ago modified 4mo ago also EUVD-2013-6209

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

Summary

(1) impl_db2.py and (2) impl_mongodb.py in OpenStack Ceilometer 2013.2 and earlier, when the logging level is set to INFO, logs the connection string from ceilometer.conf, which allows local users to obtain sensitive information (the DB2 or MongoDB password) by reading the log file.

Patch / fix

  • ceilometer Debian 14, Debian 13, Debian 12 2013.2-4

debian advisories DEBIAN-CVE-2013-6384

Is CVE-2013-6384 in your stack? 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-6384 updated cvss 4.6

OpenStack: Ceilometer DB2/MongoDB backend password leak

  • Red Hat OpenStack Platform 3 openstack-ceilometer Red Hat OpenStack Platform 4 openstack-ceilometer
    affected: no fix available

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

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

Exploits and checks

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

CVSS scores

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

Classification

Weakness
  • CWE-532 Insertion of Sensitive Information into Log File

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.