GHSA-2cvf-r9jm-4qm9 is a medium-severity (CVSS 4) CWE-532 vulnerability in ceilometer. A fix is available for ceilometer — see the affected versions and patch details below.
Ceilometer Prints Sensitive Configuration Data to Log
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-2cvf-r9jm-4qm9 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
ceilometerReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
A vulnerability was found in ceilometer before version 12.0.0.0rc1. An Information Exposure in ceilometer-agent prints sensitive configuration data to log files without DEBUG logging being activated.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | ceilometer | all versions | 12.0.0.0rc1pip install --upgrade 'ceilometer==12.0.0.0rc1' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ceilometer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ceilometer to 12.0.0.0rc1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2cvf-r9jm-4qm9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2cvf-r9jm-4qm9 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-2cvf-r9jm-4qm9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenStack Platform 10.0 (Newton) | openstack-ceilometer-1:7.1.1-9.el7ost | RHSA-2019:0919 |
| Red Hat OpenStack Platform 13.0 (Queens) | openstack-ceilometer-1:10.0.1-6.el7ost | RHSA-2019:0566 |
| Red Hat OpenStack Platform 14.0 (Rocky) | openstack-ceilometer-1:11.0.2-0.20190117115822.50f268f.el7ost | RHSA-2019:0580 |
Frequently Asked Questions
Is GHSA-2cvf-r9jm-4qm9 in your dependencies?
O3 Security finds GHSA-2cvf-r9jm-4qm9 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.