Summary
hyper's HTTP server code had a flaw that incorrectly understands some requests with multiple transfer-encoding headers to have a chunked payload, when it should have been rejected as illegal. This combined with an upstream HTTP proxy that understands the request payload boundary differently can result in "request smuggling" or "desync attacks".
Vulnerability
The flaw was introduced in hyperium/hyper@26417fc, released in v0.12.0.
Consider this example request:
POST /yolo HTTP/1.1
Transfer-Encoding: chunked
Transfer-Encoding: cow
This request should be rejected, according to RFC 7230, since it has a Transfer-Encoding header, but after folding, it does not end in chunked. hyper would notice the chunked in the first line, and then check the second line, and thanks to a missing boolean assignment, not set the error condition. hyper would treat the payload as being chunked. By differing from the spec, it is possible to send requests like these to endpoints that have different HTTP implementations, with different interpretations of the payload semantics, and cause "desync attacks".
There are several parts of the spec that must also be checked, and hyper correctly handles all of those. Additionally, hyper's client does not allow sending requests with improper headers, so the misunderstanding cannot be propagated further.
Read more about desync attacks: https://portswigger.net/research/http-desync-attacks-request-smuggling-reborn
Impact
To determine if vulnerable, all these things must be true:
- Using hyper as an HTTP server. The client is not affected.
- Using HTTP/1.1. HTTP/2 does not use
transfer-encoding.
- Using a vulnerable HTTP proxy upstream to hyper. If an upstream proxy correctly rejects the illegal transfer-encoding headers, the desync attack cannot succeed. If there is no proxy upstream of hyper, hyper cannot start the desync attack, as the client will repair the headers before forwarding.
Patches
We have released and backported the following patch versions:
Workarounds
Besides upgrading hyper, you can take the following options:
- Reject requests that contain a
transfer-encoding header.
- Ensure any upstream proxy handles
transfer-encoding correctly.
Credits
This issue was initially reported by ZeddYu Lu From Qi An Xin Technology Research Institute.
References
ZeddYu Analyst
Summary
hyper's HTTP server code had a flaw that incorrectly understands some requests with multiple transfer-encoding headers to have a chunked payload, when it should have been rejected as illegal. This combined with an upstream HTTP proxy that understands the request payload boundary differently can result in "request smuggling" or "desync attacks".
Vulnerability
The flaw was introduced in hyperium/hyper@26417fc, released in v0.12.0.
Consider this example request:
This request should be rejected, according to RFC 7230, since it has a
Transfer-Encodingheader, but after folding, it does not end inchunked. hyper would notice thechunkedin the first line, and then check the second line, and thanks to a missing boolean assignment, not set the error condition. hyper would treat the payload as beingchunked. By differing from the spec, it is possible to send requests like these to endpoints that have different HTTP implementations, with different interpretations of the payload semantics, and cause "desync attacks".There are several parts of the spec that must also be checked, and hyper correctly handles all of those. Additionally, hyper's client does not allow sending requests with improper headers, so the misunderstanding cannot be propagated further.
Read more about desync attacks: https://portswigger.net/research/http-desync-attacks-request-smuggling-reborn
Impact
To determine if vulnerable, all these things must be true:
transfer-encoding.Patches
We have released and backported the following patch versions:
Workarounds
Besides upgrading hyper, you can take the following options:
transfer-encodingheader.transfer-encodingcorrectly.Credits
This issue was initially reported by ZeddYu Lu From Qi An Xin Technology Research Institute.
References