CVE-2015-5144: n/a vulnerability

CVE-2015-5144: Django before 1.4.21, 1.5.x through 1.6.x, 1.7.x before 1.7.9, and 1.8.x before 1.8.3 uses an incorrect reg...

Django before 1.4.21, 1.5.x through 1.6.x, 1.7.x before 1.7.9, and 1.8.x before 1.8.3 uses an incorrect regular expression, which allows remote attackers to inject arbitrary headers and conduct HTTP response splitting attacks via a newline character in an (1) email message to the EmailValidator, a (2) URL to the URLValidator, or unspecified vectors to the (3) validate_ipv4_address or (4) validate_slug validator.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 06:32 UTC (UTC+00:00)

Security readout for executives and security teams

Older Django releases accepted newline characters in some validators. An attacker could submit specially crafted input that passes validation and may cause extra HTTP headers to be injected, enabling HTTP response splitting in affected applications. Exposure is most likely in legacy Django applications that accept untrusted input into the named validators, especially if validated values influence HTTP response headers. Current supported Django versions are not identified as affected in the provided sources. Treat this as a legacy-platform remediation issue. Prioritize externally reachable Django applications and systems still pinned to 2015-era branches, but there is no provided evidence of active exploitation or a critical severity rating. Mitigation focus: Upgrade Django to 1.4.21, 1.7.9, 1.8.3, or a later supported release.; Replace Django 1.5.x or 1.6.x deployments with a fixed supported branch.; Apply distribution vendor updates from Debian, Ubuntu, Fedora, Gentoo, or openSUSE where applicable..

Prepared: Jun 13, 2026, 22:22 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2015-5144 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Jul 14, 2015, 17:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
GLSA-201510-06CVE reference · vendor-advisory, x_refsource_GENTOO
https://www.djangoproject.com/weblog/2015/jul/08/security-releases/CVE reference · x_refsource_CONFIRM

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.