Django Filter
Approved changes feed: RSS · Atom
cpe:2.3:a:django-filter_project:django-filter:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Django Filter Project (d239a559-4faf-5c36-9b70-26150074348b) |
|---|---|
| Product | Django Filter (86de5bca-a3d7-52e9-bffb-df1bf458e2f9) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/carltongibson/django-filter |
purl2cpe | 2026-06-01 10:12:47.895531 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2020-15225 |
vulnerable | 2026-06-08 05:19:25.544130 |
Denial of Service vulnerability in django-filter
HIGH (7.5)
django-filter is a generic system for filtering Django QuerySets based on user selections. In django-filter before version 2.4.0, automatically generated `NumberFilter` instances, whose value was later converted to an integer, were subject to potential DoS from maliciously input using exponential format with sufficiently large exponents. Version 2.4.0+ applies a `MaxValueValidator` with a a default `limit_value` of 1e50 to the form field used by `NumberFilter` instances. In addition, `NumberFilter` implements the new `get_max_validator()` which should return a configured validator instance to customise the limit, or else `None` to disable the additional validation. Users may manually apply an equivalent validator if they are not able to upgrade.
Published: 2021-04-29T00:00:00.000Z
Updated: 2024-08-04T13:08:22.886Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.