Approved changes feed: RSS · Atom
cpe:2.3:a:djangoproject:django:1.2.1:2:*:*:*:*:*:*
part: a version: 1.2.1 update: 2
| Vendor | Djangoproject (070db687-4713-5da4-80b0-4a67baf0d0d4) |
|---|---|
| Product | Django (b34a5fd0-fae8-5096-941f-bded7e4dd228) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:docker/django/django |
purl2cpe | 2026-06-01 10:17:26.754501 |
pkg:github/django/django |
purl2cpe | 2026-06-01 10:17:26.754502 |
pkg:pypi/django |
purl2cpe | 2026-06-01 10:17:26.754504 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2011-4140 |
vulnerable | 2026-06-08 04:59:29.681487 |
Details available
The CSRF protection mechanism in Django through 1.2.7 and 1.3.x through 1.3.1 does not properly handle web-server configurations supporting arbitrary HTTP Host headers, which allows remote attackers to trigger unauthenticated forged requests via vectors involving a DNS CNAME record and a web page containing JavaScript code.
Published: 2011-10-19T10:00:00.000Z
Updated: 2024-08-07T00:01:51.120Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2011-4139 |
vulnerable | 2026-06-08 04:59:29.680646 |
Details available
Django before 1.2.7 and 1.3.x before 1.3.1 uses a request's HTTP Host header to construct a full URL in certain circumstances, which allows remote attackers to conduct cache poisoning attacks via a crafted request.
Published: 2011-10-19T10:00:00.000Z
Updated: 2024-08-07T00:01:50.429Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2011-4138 |
vulnerable | 2026-06-08 04:59:29.679511 |
Details available
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-19T10:00:00.000Z
Updated: 2024-08-07T00:01:51.120Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2011-4137 |
vulnerable | 2026-06-08 04:59:29.678502 |
Details available
The verify_exists functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 relies on Python libraries that attempt access to an arbitrary URL with no timeout, which allows remote attackers to cause a denial of service (resource consumption) via a URL associated with (1) a slow response, (2) a completed TCP connection with no application data sent, or (3) a large amount of application data, a related issue to CVE-2011-1521.
Published: 2011-10-19T10:00:00.000Z
Updated: 2024-08-07T00:01:50.805Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2011-4136 |
vulnerable | 2026-06-08 04:59:29.669221 |
Details available
django.contrib.sessions in Django before 1.2.7 and 1.3.x before 1.3.1, when session data is stored in the cache, uses the root namespace for both session identifiers and application-data keys, which allows remote attackers to modify a session by triggering use of a key that is equal to that session's identifier.
Published: 2011-10-19T10:00:00.000Z
Updated: 2024-08-07T00:01:50.498Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2010-3082 |
vulnerable | 2026-06-08 04:55:12.580024 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.