Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

CVE-2021-21299— Multiple Transfer-Encoding headers misinterprets request payload

Quick assessment

Affected
hyperium hyper
Exploitation
High exploitation probability; assess promptly
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

hyper crate for Rust是一款基于Rust的HTTP库。 hyper crate for Rust 中存在环境问题漏洞，该漏洞源于网络系统或产品的环境因素不合理。

CVSS 4.8 · Medium EPSS 4.77% · P91
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2021-21299

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Multiple Transfer-Encoding headers misinterprets request payload
Source: CVE Program / CVE List V5
Vulnerability Description
hyper is an open-source HTTP library for Rust (crates.io). In hyper from version 0.12.0 and before versions 0.13.10 and 0.14.3 there is a vulnerability that can enable a request smuggling attack. The 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". To determine if vulnerable, all these things must be true: 1) Using hyper as an HTTP server (the client is not affected), 2) Using HTTP/1.1 (HTTP/2 does not use transfer-encoding), 3) 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. This is fixed in versions 0.14.3 and 0.13.10. As a workaround one can take the following options: 1) Reject requests that contain a `transfer-encoding` header, 2) Ensure any upstream proxy handles `transfer-encoding` correctly.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
HTTP请求的解释不一致性(HTTP请求私运)
Source: CVE Program / CVE List V5
Vulnerability Title
hyper crate for Rust 环境问题漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
hyper crate for Rust是一款基于Rust的HTTP库。 hyper crate for Rust 中存在环境问题漏洞，该漏洞源于网络系统或产品的环境因素不合理。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
hyperium hyper < 0.13.10 -

II. Public POCs for CVE-2021-21299

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2021-21299

请登录查看更多情报信息。

Patches & Fixes for CVE-2021-21299 (1)

Vendor Advisories for CVE-2021-21299 (1)

Security Blog Posts for CVE-2021-21299 (1)

Other References for CVE-2021-21299 (2)

IV. Related Vulnerabilities

Same product: hyper
Same vendor: hyperium
Same weakness: CWE-444

V. Comments for CVE-2021-21299

No comments yet

Leave a comment