CVE-2019-17134 — octavia
CRITICALCVE-2019-17134 is a critical-severity (CVSS 9.1) Improper Authentication vulnerability in octavia. 1 public exploit reference exists, so weaponization risk is real. A fix is available for octavia — see the affected versions and patch details below.
OpenStack Octavia Amphora-Agent not requiring Client-Certificate
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
CVE-2019-17134 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 377,166 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
octavia🐍octavia🐍octaviaReal-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
Amphora Images in OpenStack Octavia >=0.10.0 <2.1.2, >=3.0.0 <3.2.0, >=4.0.0 <4.1.0 allows anyone with access to the management network to bypass client-certificate based authentication and retrieve information or issue configuration commands via simple HTTP requests to the Agent on port https/9443, because the cmd/agent.py gunicorn cert_reqs option is True but is supposed to be ssl.CERT_REQUIRED.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | octavia | ≥ 0.10.0&&< 2.1.2 | 2.1.2pip install --upgrade 'octavia==2.1.2' |
| 🐍PyPI | octavia | ≥ 3.0.0&&< 3.2.0 | 3.2.0pip install --upgrade 'octavia==3.2.0' |
| 🐍PyPI | octavia | ≥ 4.0.0&&< 4.1.0 | 4.1.0pip install --upgrade 'octavia==4.1.0' |
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 octavia, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update octavia to 2.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-17134 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 CVE-2019-17134 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2019-17134. 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 13.0 (Queens) | openstack-octavia-0:2.1.2-1.el7ost | RHSA-2019:3788 |
| Red Hat OpenStack Platform 14.0 (Rocky) | openstack-octavia-0:3.1.0-3.el7ost | RHSA-2019:3743 |
| Red Hat OpenStack Platform 15.0 (Stein) | openstack-octavia-0:4.1.2-0.20200114080449.5a71643.el8ost | RHSA-2020:0721 |
Frequently Asked Questions
Is CVE-2019-17134 in your dependencies?
O3 Security finds CVE-2019-17134 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.