CVE-2020-9543 — manila
HIGHCVE-2020-9543 is a high-severity (CVSS 8.3) Incorrect Default Permissions vulnerability in manila. 1 public exploit reference exists, so weaponization risk is real. A fix is available for manila — see the affected versions and patch details below.
OpenStack Manila Unprivileged users can retrieve, use and manipulate share networks
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-2020-9543 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
manila🐍manila🐍manilaReal-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
OpenStack Manila <7.4.1, >=8.0.0 <8.1.1, and >=9.0.0 <9.1.1 allows attackers to view, update, delete, or share resources that do not belong to them, because of a context-free lookup of a UUID. Attackers may also create resources, such as shared file systems and groups of shares on such share networks.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | manila | all versions | 7.4.1pip install --upgrade 'manila==7.4.1' |
| 🐍PyPI | manila | ≥ 8.0.0&&< 8.1.1 | 8.1.1pip install --upgrade 'manila==8.1.1' |
| 🐍PyPI | manila | ≥ 9.0.0&&< 9.1.1 | 9.1.1pip install --upgrade 'manila==9.1.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 manila, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update manila to 7.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-9543 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-2020-9543 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2020-9543. 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-manila-1:6.3.2-3.el7ost | RHSA-2020:2729 |
| Red Hat OpenStack Platform 15.0 (Stein) | openstack-manila-1:8.1.1-0.20200311070441.17b29e2.el8ost | RHSA-2020:1326 |
| Red Hat OpenStack Platform 16.0 (Train) | openstack-manila-1:9.1.2-0.20200405045746.f071a43.el8ost | RHSA-2020:2165 |
Frequently Asked Questions
Is CVE-2020-9543 in your dependencies?
O3 Security finds CVE-2020-9543 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.