Improper header parsing. An attacker could sneak in a newline (\n
) into both the header names and values. While the specification states that \r\n\r\n
is used to terminate the header list, many servers in the wild will also accept \n\n
.
The issue is patched in 1.9.1 and 2.4.5.
There are no known workarounds.
{ "nvd_published_at": "2023-04-17T22:15:09Z", "cwe_ids": [ "CWE-436" ], "severity": "MODERATE", "github_reviewed": true, "github_reviewed_at": "2023-04-19T18:25:53Z" }