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

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

CVE-2020-26281— request smuggling in async-h1

Quick assessment

Affected
http-rs async-h1
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Http-rs Async-h1是Http-rs团队的一个基于Rust语言的异步Http解析器。 async-h1 2.3.0之前版本存在安全漏洞，该漏洞源于存在请求走私漏洞。此漏洞影响任何在反向代理后使用async-h1的web服务器，包括所有此类Tide应用程序。如果服务器没有读取超过缓冲区长度的请求体，async-h1将尝试从该偏移量开始的请求体内容中读取后续请求。

CVSS 6.8 · Medium EPSS 1.01% · P61
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2020-26281

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
request smuggling in async-h1
Source: CVE Program / CVE List V5
Vulnerability Description
async-h1 is an asynchronous HTTP/1.1 parser for Rust (crates.io). There is a request smuggling vulnerability in async-h1 before version 2.3.0. This vulnerability affects any webserver that uses async-h1 behind a reverse proxy, including all such Tide applications. If the server does not read the body of a request which is longer than some buffer length, async-h1 will attempt to read a subsequent request from the body content starting at that offset into the body. One way to exploit this vulnerability would be for an adversary to craft a request such that the body contains a request that would not be noticed by a reverse proxy, allowing it to forge forwarded/x-forwarded headers. If an application trusted the authenticity of these headers, it could be misled by the smuggled request. Another potential concern with this vulnerability is that if a reverse proxy is sending multiple http clients' requests along the same keep-alive connection, it would be possible for the smuggled request to specify a long content and capture another user's request in its body. This content could be captured in a post request to an endpoint that allows the content to be subsequently retrieved by the adversary. This has been addressed in async-h1 2.3.0 and previous versions have been yanked.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
HTTP请求的解释不一致性(HTTP请求私运)
Source: CVE Program / CVE List V5
Vulnerability Title
Http-rs Async-h1 环境问题漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Http-rs Async-h1是Http-rs团队的一个基于Rust语言的异步Http解析器。 async-h1 2.3.0之前版本存在安全漏洞，该漏洞源于存在请求走私漏洞。此漏洞影响任何在反向代理后使用async-h1的web服务器，包括所有此类Tide应用程序。如果服务器没有读取超过缓冲区长度的请求体，async-h1将尝试从该偏移量开始的请求体内容中读取后续请求。
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
http-rs async-h1 < 2.3.0 -

II. Public POCs for CVE-2020-26281

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

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2020-26281

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

Vendor Advisories for CVE-2020-26281 (1)

Other References for CVE-2020-26281 (1)

IV. Related Vulnerabilities

Same weakness: CWE-444

V. Comments for CVE-2020-26281

No comments yet

Leave a comment