CVSS: 6.1EPSS: 0%CPEs: 1EXPL: 0CVE-2020-36202
https://notcve.org/view.php?id=CVE-2020-36202
An issue was discovered in the async-h1 crate before 2.3.0 for Rust. Request smuggling can occur when used behind a reverse proxy. Se detectó un problema en la crate async-h1 versiones anteriores a 2.3.0 para Rust. El trafico no autorizado de peticiones puede ocurrir cuando se utiliza detrás de un proxy inverso • https://rustsec.org/advisories/RUSTSEC-2020-0093.html • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •
CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0CVE-2020-26281 – request smuggling in async-h1
https://notcve.org/view.php?id=CVE-2020-26281
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. • https://github.com/http-rs/async-h1/releases/tag/v2.3.0 https://github.com/http-rs/async-h1/security/advisories/GHSA-4vr9-8cjf-vf9c • CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') •