HIGH 7.5 PyPI
Django Might Allow CSRF Requests via URL Verification
GHSA-wxg3-mfph-qg9w · CVE-2011-4138 · PYSEC-2011-3
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
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.
References
- ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2011-4138
- WEB 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
- PACKAGE https://github.com/django/django
- WEB 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
Ready to move
Start Securing
Free, no credit card | First findings in minutes