GoogleOSV:GHSA-WXG3-MFPH-QG9WDjango Might Allow CSRF Requests via URL Verification
6.8 Medium
AI Score
Confidence
High
5 Medium
CVSS2
Access Vector
NETWORK
Access Complexity
LOW
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
NONE
Availability Impact
NONE
AV:N/AC:L/Au:N/C:P/I:N/A:N
0.007 Low
EPSS
Percentile
80.6%
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
openwall.com/lists/oss-security/2011/09/11/1
openwall.com/lists/oss-security/2011/09/13/2
www.debian.org/security/2011/dsa-2332
bugzilla.redhat.com/show_bug.cgi?id=737366
github.com/django/django
github.com/django/django/commit/1a76dbefdfc60e2d5954c0ba614c3d054ba9c3f0
github.com/django/django/commit/7268f8af86186518821d775c530d5558fd726930
hermes.opensuse.org/messages/14700881
nvd.nist.gov/vuln/detail/CVE-2011-4138
www.djangoproject.com/weblog/2011/sep/09
www.djangoproject.com/weblog/2011/sep/10/127
Related
6.8 Medium
AI Score
Confidence
High
5 Medium
CVSS2
Access Vector
NETWORK
Access Complexity
LOW
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
NONE
Availability Impact
NONE
AV:N/AC:L/Au:N/C:P/I:N/A:N
0.007 Low
EPSS
Percentile
80.6%