CVE-2022-23833: An issue was discovered in MultiPartParser in Django 2.2 before 2.2.27, 3.2 before 3.2.12, and 4.0 before 4.0.2.
Noroxi assessment
Priority: Plan (action score 45/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 49.5% (FIRST EPSS); higher than 98.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: python-django (Debian:10) 1:1.11.29-1+deb10u4; python-django (Debian:11) 2:2.2.28-1~deb11u1; python-django (Debian:12) 2:3.2.12-1.
Add it to your regular patch cycle. Upgrade to python-django (Debian:10) 1:1.11.29-1+deb10u4; python-django (Debian:11) 2:2.2.28-1~deb11u1; python-django (Debian:12) 2:3.2.12-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An issue was discovered in MultiPartParser in Django 2.2 before 2.2.27, 3.2 before 3.2.12, and 4.0 before 4.0.2. Passing certain inputs to multipart forms could result in an infinite loop when parsing files.
- Published
- Feb 2, 2022
- Updated
- Jun 17, 2026
- EPSS
- 49.5% · 98th percentile
- CWE
- CWE-835
Report tools
Action score
45
Plan
Add it to your regular patch cycle.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 15 / 30 · 49.5%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| djangoproject | django | cpe:2.3:a:djangoproject:django |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- djangoproject django2.2 and later · before 2.2.27
- djangoproject django3.2 and later · before 3.2.12
- djangoproject django4.0 and later · before 4.0.2
- fedoraproject fedora34
- fedoraproject fedora35
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:10 | python-django | before 1:1.11.29-1+deb10u4 | 1:1.11.29-1+deb10u4 |
| Debian:11 | python-django | before 2:2.2.28-1~deb11u1 | 2:2.2.28-1~deb11u1 |
| Debian:12 | python-django | before 2:3.2.12-1 | 2:3.2.12-1 |
| Debian:9 | python-django | before 1:1.10.7-2+deb9u15 | 1:1.10.7-2+deb9u15 |
| openSUSE:Leap 15.3 | python-Django | before 2.2.28-bp153.2.3.1 | 2.2.28-bp153.2.3.1 |
| openSUSE:Tumbleweed | python-Django | before 4.0.2-1.1 | 4.0.2-1.1 |
| openSUSE:Tumbleweed | python-Django | before 5.1.5-1.1 | 5.1.5-1.1 |
| PyPI | django | from 2.2 · before 2.2.27 | 2.2.27 |
| PyPI | django | from 3.2 · before 3.2.12 | 3.2.12 |
| PyPI | django | from 4.0 · before 4.0.2 | 4.0.2 |
| Red Hat:openstack:16.1::el8 | python-django20-bash-completion | before 0:2.0.13-18.el8ost | 0:2.0.13-18.el8ost |
| Red Hat:openstack:16.2::el8 | python-django20 | before 0:2.0.13-18.el8ost | 0:2.0.13-18.el8ost |
| Red Hat:openstack:16.2::el8 | python3-django20 | before 0:2.0.13-18.el8ost | 0:2.0.13-18.el8ost |
| SUSE:HPE Helion OpenStack 8 | python-Django | before 1.11.29-3.39.1 | 1.11.29-3.39.1 |
| SUSE:HPE Helion OpenStack 8 | venv-openstack-aodh | before 5.1.1~dev7-12.37.1 | 5.1.1~dev7-12.37.1 |
| SUSE:HPE Helion OpenStack 8 | venv-openstack-barbican | before 5.0.2~dev3-12.38.1 | 5.0.2~dev3-12.38.1 |
| SUSE:HPE Helion OpenStack 8 | venv-openstack-ceilometer | before 9.0.8~dev7-12.35.1 | 9.0.8~dev7-12.35.1 |
| SUSE:HPE Helion OpenStack 8 | venv-openstack-cinder | before 11.2.3~dev29-14.39.1 | 11.2.3~dev29-14.39.1 |
| SUSE:HPE Helion OpenStack 8 | venv-openstack-designate | before 5.0.3~dev7-12.36.1 | 5.0.3~dev7-12.36.1 |
| SUSE:HPE Helion OpenStack 8 | venv-openstack-freezer | before 5.0.0.0~xrc2~dev2-10.33.1 | 5.0.0.0~xrc2~dev2-10.33.1 |
| SUSE:HPE Helion OpenStack 8 | venv-openstack-glance | before 15.0.3~dev3-12.36.1 | 15.0.3~dev3-12.36.1 |
| SUSE:HPE Helion OpenStack 8 | venv-openstack-heat | before 9.0.8~dev22-12.40.1 | 9.0.8~dev22-12.40.1 |
| SUSE:HPE Helion OpenStack 8 | venv-openstack-horizon-hpe | before 12.0.5~dev6-14.43.2 | 12.0.5~dev6-14.43.2 |
| SUSE:HPE Helion OpenStack 8 | venv-openstack-ironic | before 9.1.8~dev8-12.38.1 | 9.1.8~dev8-12.38.1 |
+32
Same product
djangoproject: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-34265An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6.61This week
- CVE-2020-7471Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 allows SQL Injection if untrusted data is used as a StringAgg delimiter 59Plan
- CVE-2019-19844Django before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 allows account takeover.55Plan
Published before and after this one in the same product
- ← EarlierCVE-2021-45452Jan 4, 2022 · Storage.save in Django 2.2 before 2.2.26, 3.2 before 3.2.11, and 4.0 before 4.0.1 allows directory traversal if crafted filenames are direct22Monitor
- ← EarlierCVE-2022-22818Feb 2, 2022 · The {% debug %} template tag in Django 2.2 before 2.2.27, 3.2 before 3.2.12, and 4.0 before 4.0.2 does not properly encode the current conte25Monitor
- Later →CVE-2022-28346Apr 12, 2022 · An issue was discovered in Django 2.2 before 2.2.28, 3.2 before 3.2.13, and 4.0 before 4.0.4.45Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:python-django | 2:3.2.12-1 · Debian:12 | Package registry (OSV) |
| opensuse:python-Django | 2.2.28-bp153.2.3.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| PyPI:django | 2.2.27 | Package registry (OSV) |
| PyPI:django | 3.2.12 | Package registry (OSV) |
| PyPI:django | 4.0.2 | Package registry (OSV) |
| red hat:python-django20 | 0:2.0.13-18.el8ost · Red Hat:openstack:16.2::el8 | Package registry (OSV) |
| red hat:python-django20-bash-completion | 0:2.0.13-18.el8ost · Red Hat:openstack:16.1::el8 | Package registry (OSV) |
| red hat:python3-django20 | 0:2.0.13-18.el8ost · Red Hat:openstack:16.2::el8 | Package registry (OSV) |
| suse:python-Django | 2.2.28-bp153.2.3.1 · SUSE:Package Hub 15 SP3 | Package registry (OSV) |
| suse:python-Django1 | 1.11.29-3.37.1 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:venv-openstack-barbican | 7.0.1~dev24-3.30.1 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:venv-openstack-cinder | 13.0.10~dev23-3.33.1 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:venv-openstack-designate | 7.0.2~dev2-3.30.1 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:venv-openstack-glance | 17.0.1~dev30-3.28.1 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:venv-openstack-heat | 11.0.4~dev4-3.30.1 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:venv-openstack-horizon | 14.1.1~dev11-4.34.2 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:venv-openstack-ironic | 11.1.5~dev17-4.28.1 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:venv-openstack-keystone | 14.2.1~dev7-3.31.1 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:venv-openstack-magnum | 7.2.1~dev1-4.30.1 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:venv-openstack-manila | 7.4.2~dev60-3.36.1 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:venv-openstack-monasca | 2.7.1~dev10-3.32.1 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- github.com/django/django/commit/c477b761804984c932704554ad35f78a2e230c6a
- github.com/django/django/commit/d16133568ef9c9b42cb7a08bdf9ff3feec2e5468
- github.com/django/django/commit/f9c7d48fdd6f198a6494a9202f90242f176e4fc9
- groups.google.com/forum/#%21forum/django-announce
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/B4SQG2EAF4WCI2SLRL6XRDJ3RPK3ZRDV/
- security.netapp.com/advisory/ntap-20220221-0003/
- www.debian.org/security/2022/dsa-5254
- www.djangoproject.com/weblog/2022/feb/01/security-releases/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.