From 5233609919f8b619a925e0467bc6807639605538 Mon Sep 17 00:00:00 2001 From: Vinzent Steinberg Date: Mon, 7 Oct 2019 15:28:30 +0200 Subject: [PATCH] Fix escapes in hyper advisory Fixes #159. --- crates/hyper/RUSTSEC-2017-0002.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/crates/hyper/RUSTSEC-2017-0002.toml b/crates/hyper/RUSTSEC-2017-0002.toml index b24b9aa..ab71e11 100644 --- a/crates/hyper/RUSTSEC-2017-0002.toml +++ b/crates/hyper/RUSTSEC-2017-0002.toml @@ -6,7 +6,7 @@ date = "2017-01-23" url = "https://github.com/hyperium/hyper/wiki/Security-001" title = "headers containing newline characters can split messages" description = """ -Serializing of headers to the socket did not filter the values for newline bytes (\r or \n), +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.