{"id":"EUVD-2021-2157","enisaUuid":"cde41fe7-ac68-343a-8f13-f4522a202b9e","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\u0027 requests along the same keep-alive connection, it would be possible for the smuggled request to specify a long content and capture another user\u0027s 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.","datePublished":"Dec 21, 2020, 9:50:13 PM","dateUpdated":"Aug 4, 2024, 3:56:03 PM","baseScore":6.8,"baseScoreVersion":"3.1","baseScoreVector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N","references":"https://github.com/http-rs/async-h1/security/advisories/GHSA-4vr9-8cjf-vf9c\nhttps://github.com/http-rs/async-h1/releases/tag/v2.3.0\n","aliases":"CVE-2020-26281\nGHSA-4vr9-8cjf-vf9c\n","assigner":"GitHub_M","epss":1.02,"enisaIdProduct":[{"id":"8e3d3f6e-015c-3358-bc62-b64234ead5b4","product":{"name":"async-h1","vendor":{"name":"http-rs"}},"product_version":"\u003c 2.3.0"}],"enisaIdVendor":[{"id":"9965ebd0-5437-3a25-9553-cc63d7a9c922","vendor":{"name":"http-rs"}}],"enisaIdVulnerability":[{"id":"49f1c4ef-9ebc-300f-9467-0a1db12b7683","vulnerability":{"id":"GHSA-4vr9-8cjf-vf9c","description":"Async-h1 request smuggling possible with long unread bodies","datePublished":"Oct 12, 2021, 4:00:37 PM","dateUpdated":"Oct 8, 2021, 10:14:28 PM","baseScore":null,"references":"https://github.com/http-rs/async-h1/security/advisories/GHSA-4vr9-8cjf-vf9c\nhttps://nvd.nist.gov/vuln/detail/CVE-2020-26281\nhttps://github.com/http-rs/async-h1\nhttps://github.com/http-rs/async-h1/releases/tag/v2.3.0\nhttps://rustsec.org/advisories/RUSTSEC-2020-0093.html\n","enisa_id":"EUVD-2021-2157\n","aliases":"GHSA-4vr9-8cjf-vf9c\nCVE-2020-26281\n","epss":0.0,"dataProcessed":"Nov 15, 2026, 2:06:27 AM","vulnerabilityProduct":[],"vulnerabilityVendor":[]}},{"id":"d2cb714a-2ac3-3f35-bea1-815fc7ee7187","vulnerability":{"id":"CVE-2020-26281","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\u0027 requests along the same keep-alive connection, it would be possible for the smuggled request to specify a long content and capture another user\u0027s 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.","datePublished":"Dec 21, 2020, 9:50:13 PM","dateUpdated":"Aug 4, 2024, 3:56:03 PM","status":"PUBLISHED","baseScore":6.8,"baseScoreVersion":"3.1","baseScoreVector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N","references":"https://github.com/http-rs/async-h1/security/advisories/GHSA-4vr9-8cjf-vf9c\nhttps://github.com/http-rs/async-h1/releases/tag/v2.3.0\n","enisa_id":"EUVD-2021-2157\n","assigner":"GitHub_M","epss":1.02,"dataProcessed":"Nov 18, 2026, 7:21:45 AM","vulnerabilityProduct":[{"id":"04ff9d68-eb07-326f-9615-dd96cccb89a5","product":{"name":"async-h1","vendor":{"name":"http-rs"}},"product_version":"\u003c 2.3.0"}],"vulnerabilityVendor":[{"id":"679619d1-964c-3c45-a702-fc4a4122d0ed","vendor":{"name":"http-rs"}}]}}],"enisaIdAdvisory":[]}