GHSA-wmqq-r32m-87c5 — oslo-utils
MEDIUMGHSA-wmqq-r32m-87c5 is a medium-severity (CVSS 4.9) CWE-522 vulnerability in oslo-utils. 1 public exploit reference exists, so weaponization risk is real. A fix is available for oslo-utils — see the affected versions and patch details below.
python-oslo-utils has improper password parsing
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-wmqq-r32m-87c5 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
oslo-utilsReal-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 flaw was found in python-oslo-utils. Due to improper parsing, passwords with a double quote ( " ) in them cause incorrect masking in debug logs, causing any part of the password after the double quote to be plaintext.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | oslo-utils | all versions | 4.10.1pip install --upgrade 'oslo-utils==4.10.1' |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for oslo-utils, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update oslo-utils to 4.10.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wmqq-r32m-87c5 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-wmqq-r32m-87c5 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-wmqq-r32m-87c5. 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 16.1 | python-oslo-utils-0:3.41.6-1.20220426095230.f4deaad.el8ost | RHSA-2022:8873 |
| Red Hat OpenStack Platform 16.2 | python-oslo-utils-0:3.41.6-2.20220111011750.el8ost | RHSA-2022:0993 |
Frequently Asked Questions
Is GHSA-wmqq-r32m-87c5 in your dependencies?
O3 Security finds GHSA-wmqq-r32m-87c5 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.