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.
Published: 2011-10-19
Score: 5.0 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

No analysis available yet.

Remediation

No remediation available yet.

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.

Subscriptions

Djangoproject Django
cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2024-08-07T00:01:51.120Z

Reserved: 2011-10-19T00:00:00.000Z

Link: CVE-2011-4138

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2011-10-19T10:55:04.457

Modified: 2025-04-11T00:51:21.963

Link: CVE-2011-4138

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses