PortSwigger shows HTTP header injection can be escalated to a CRLF-powered desync
RESEARCHredteam/daily · 1 source
- Severity
- Medium
- Sources
- 1
What happened
PortSwigger Research describes escalating HTTP header injection to a CRLF-powered desync, allowing an attacker to serve redirects to their collaborator host to random users. The article says this is achievable in a single prompt and that a new scan check has been introduced. The source excerpt is truncated and gives no CVE IDs, affected products or versions. Defenders should use the new scan check to test for header injection and review how CR and LF characters are handled in header values.
For security analysts · Written by AI from 1 source · Wrong?
What to do
- Use the newly introduced PortSwigger scan check to test applications for HTTP header injection.
- Read the full PortSwigger article for details of the CRLF desync technique before assessing exposure.
Written by AI from the sources, checked against them
Full story timeline · 1 update
Who reported · 1 outlet
PortSwigger Research