tree 0ef853ad8b4b43814a3bed46cc06a525040528af
parent 426c9ed24440438262691dd1d36e15819cdb3be8
author Amaury Denoyelle <adenoyelle@haproxy.com> 1719564199 +0200
committer Christopher Faulet <cfaulet@haproxy.com> 1719995347 +0200

BUG/MEDIUM: h3: ensure the ":method" pseudo header is totally valid

Ensure pseudo-header method is only constitued of valid characters
according to RFC 9110. If an invalid value is found, the request is
rejected and stream is resetted.

Previously only characters forbidden in headers were rejected (NUL/CR/LF),
but this is insufficient for :method, where some other forbidden chars
might be used to trick a non-compliant backend server into seeing a
different path from the one seen by haproxy. Note that header injection
is not possible though.

This must be backported up to 2.6.

Many thanks to Yuki Mogi of FFRI Security Inc for the detailed report
that allowed to quicky spot, confirm and fix the problem.

(cherry picked from commit 789d4abd7328f0a745d67698e89bbb888d4d9b2c)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
(cherry picked from commit 47d13c68cf198467a94e85a1caa44484a1e2e75c)
[cf: adapted]
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
(cherry picked from commit 87fefebfbe3df218103502046a0871b235a48087)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>