Unusually Long Content-Type Length
The following analytic identifies unusually long strings in the Content-Type HTTP header sent by the client to the server. It uses data from the Stream:HTTP source, specifically evaluating the length of the…
Description
The following analytic identifies unusually long strings in the Content-Type HTTP header sent by the client to the server. It uses data from the Stream:HTTP source, specifically evaluating the length of the `cs_content_type` field. This activity is significant because excessively long Content-Type headers can indicate attempts to exploit vulnerabilities or evade detection mechanisms. If confirmed malicious, this behavior could allow attackers to execute code, manipulate data, or bypass security controls, potentially leading to unauthorized access or data breaches.
Detection logic
Known benign triggers
- Very few legitimate Content-Type fields will have a length greater than 100 characters.
MITRE ATT&CK mappings
Not mapped to ATT&CK.
No references are available for this detection.
From the source
- At source
- Open at source
- Upstream identifier
- 57a0a2bf-353f-40c1-84dc-29293f3c35b7
- Tagged by the source as
- Apache Struts VulnerabilityWeb ServerwebSplunk CloudSplunk EnterpriseSplunk Enterprise Securitynetwork
Licence
- Published under
- Apache License 2.0Read the licence
- Attribution
- Required
- Obtained under
- Apache-2.0Read the origin licence
Authorship
- Written by
- Published
- Aug 26, 2026
- Version
- 1