CVE-2011-4138

Published Oct 19, 2011 CVSS 2.0 · 5.0 Medium EPSS 2.4% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DSA Debian DSA DSA-2332-1 python-django security update
EUVD EUVD EUVD-2011-0008 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.
Github GHSA Github GHSA GHSA-wxg3-mfph-qg9w Django Might Allow CSRF Requests via URL Verification
Ubuntu USN Ubuntu USN USN-1297-1 Django vulnerabilities
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Aug 7, 2024, 12:01 AM
Reserved
Oct 19, 2011, 12:00 AM
Status
Modified
Published
Oct 19, 2011, 10:55 AM
Modified
Jun 16, 2026, 11:34 PM