# Uncontrolled Memory Consumption in Django

Advisory record · `GHSA-wh4h-v3f2-r2pp`

- **Identifiers:** `GHSA-wh4h-v3f2-r2pp` · `CVE-2019-6975` · `PYSEC-2019-18`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-770](https://cwe.mitre.org/data/definitions/770.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 12 Feb 2019
- **Updated:** 21 Feb 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 12 Feb 2019, 15:36 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `django` (PyPI): affected `>=1.11, <1.11.19 || >=2.0, <2.0.11 || >=2.1, <2.1.6`; fixed in `1.11.19`, `2.0.11`, `2.1.6`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.051, the 92nd percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 12 Feb 2019. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-wh4h-v3f2-r2pp](https://github.com/advisories/GHSA-wh4h-v3f2-r2pp)
- [OSV: GHSA-wh4h-v3f2-r2pp](https://osv.dev/vulnerability/GHSA-wh4h-v3f2-r2pp)
- <https://nvd.nist.gov/vuln/detail/CVE-2019-6975>
- <https://github.com/django/django/commit/0bbb560183fabf0533289700845dafa94951f227>
- <https://github.com/django/django/commit/1f42f82566c9d2d73aff1c42790d6b1b243f7676>
- <https://github.com/django/django/commit/40cd19055773705301c3428ed5e08a036d2091f3>
- <https://www.openwall.com/lists/oss-security/2019/02/11/1>
- <https://www.djangoproject.com/weblog/2019/feb/11/security-releases>
- <https://www.debian.org/security/2019/dsa-4476>
- <https://web.archive.org/web/20200227084713/http://www.securityfocus.com/bid/106964>
- <https://usn.ubuntu.com/3890-1>
- <https://seclists.org/bugtraq/2019/Jul/10>
- <https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HVXDOVCXLD74SHR2BENGCE2OOYYYWJHZ>
- <https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/66WMXHGBXD7GSM3PEXVCMCAGLMQYHZCU>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-wh4h-v3f2-r2pp>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-wh4h-v3f2-r2pp/>. Everything for agents: <https://agentprime.io/llms.txt>.
