GHSA-xgxc-v2qg-chmh
MEDIUMGHSA-xgxc-v2qg-chmh is a medium-severity (CVSS 5.3) vulnerability in django. O3 Security confirms whether GHSA-xgxc-v2qg-chmh is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Directory Traversal in Django
Real-World Exposure
django🐍django🐍djangoReal-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
In Django 2.2 before 2.2.20, 3.0 before 3.0.14, and 3.1 before 3.1.8, MultiPartParser allowed directory traversal via uploaded files with suitably crafted file names. Built-in upload handlers were not affected by this vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | django | ≥ 2.2a1&&< 2.2.20 | 2.2.20 |
| 🐍PyPI | django | ≥ 3.0a1&&< 3.0.14 | 3.0.14 |
| 🐍PyPI | django | ≥ 3.1a1&&< 3.1.8 | 3.1.8 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update django to 2.2.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xgxc-v2qg-chmh 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 pinpoints whether GHSA-xgxc-v2qg-chmh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-xgxc-v2qg-chmh. 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.
Although Red Hat Ansible Tower ships the flawed code, it does not use the vulnerable function i.e. "MultiPartParser" and therefore will not be updated. Red Hat Update Infrastructure ship affected version of python-django however RHUI v3 is in maintenance support phase and we are only fixing critical and important…
Frequently Asked Questions
Is GHSA-xgxc-v2qg-chmh in your dependencies?
O3 detects GHSA-xgxc-v2qg-chmh across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.