Total vulnerabilities in the database
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.6.1.
There are no known workarounds.
Software | From | Fixed in |
---|---|---|
![]() |
- | 1.6.1 |