Serializing of headers to the socket did not filter the values for newline bytes (\r or \n), which allowed for header values to split a request or response. People would not likely include newlines in the headers in their own applications, so the way for most people to exploit this is if an application constructs headers based on unsanitized user input.

This issue was fixed by replacing all newline characters with a space during serialization of a header value.

References

• https://nvd.nist.gov/vuln/detail/CVE-2017-18587
• https://rustsec.org/advisories/RUSTSEC-2017-0002.html
• https://github.com/hyperium/hyper/wiki/Security-001