GitHub Advisoryadvisory · PyPI
GHSA-wxg3-mfph-qg9w Django Might Allow CSRF Requests via URL Verification
HIGH
Official page ↗
- Aliases
- CVE-2011-4138
- Ecosystem
- PyPI
- Packages
- Django
- Severity
- High
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- Weaknesses
- CWE-20
- Reviewed
- 2024-01-16
Affected packages
• PyPI Django: < 1.2.7 → fixed in 1.2.7
• PyPI Django: >= 1.3, < 1.3.1 → fixed in 1.3.1
Description
The `verify_exists` functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 originally tests a URL's validity through a HEAD request, but then uses a GET request for the new target URL in the case of a redirect, which might allow remote attackers to trigger arbitrary GET requests with an unintended source IP address via a crafted Location header.
Related
Alias · CVE (1)
- CVE-2011-4138 The verify_exists functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 originally tests a URL's… vulnerability
Weakness · CWE (1)
- CWE-20 Improper Input Validation weakness
References
- https://nvd.nist.gov/vuln/detail/CVE-2011-4138 advisory
- https://github.com/django/django/commit/1a76dbefdfc60e2d5954c0ba614c3d054ba9c3f0 web
- https://github.com/django/django/commit/7268f8af86186518821d775c530d5558fd726930 web
- https://bugzilla.redhat.com/show_bug.cgi?id=737366 web
- https://github.com/django/django package
- https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2011-3.yaml web
- https://hermes.opensuse.org/messages/14700881 web
- https://www.djangoproject.com/weblog/2011/sep/09 web
- https://www.djangoproject.com/weblog/2011/sep/10/127 web
- http://openwall.com/lists/oss-security/2011/09/11/1 web
- http://openwall.com/lists/oss-security/2011/09/13/2 web
- http://www.debian.org/security/2011/dsa-2332 web