CVE-2023-44487 – HTTP/2 Rapid Reset Attack Vulnerability
https://notcve.org/view.php?id=CVE-2023-44487
The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023. El protocolo HTTP/2 permite una denegación de servicio (consumo de recursos del servidor) porque la cancelación de solicitudes puede restablecer muchas transmisiones rápidamente, como se explotó en la naturaleza entre agosto y octubre de 2023. A flaw was found in handling multiplexed streams in the HTTP/2 protocol. A client can repeatedly make a request for a new multiplex stream and immediately send an RST_STREAM frame to cancel it. This creates extra work for the server setting up and tearing down the streams while not hitting any server-side limit for the maximum number of active streams per connection, resulting in a denial of service due to server resource consumption. • https://github.com/imabee101/CVE-2023-44487 https://github.com/studiogangster/CVE-2023-44487 https://github.com/bcdannyboy/CVE-2023-44487 https://github.com/sigridou/CVE-2023-44487- https://github.com/ByteHackr/CVE-2023-44487 https://github.com/ReToCode/golang-CVE-2023-44487 http://www.openwall.com/lists/oss-security/2023/10/13/4 http://www.openwall.com/lists/oss-security/2023/10/13/9 http://www.openwall.com/lists/oss-security/2023/10/18/4 http://www. • CWE-400: Uncontrolled Resource Consumption •
CVE-2021-24029
https://notcve.org/view.php?id=CVE-2021-24029
A packet of death scenario is possible in mvfst via a specially crafted message during a QUIC session, which causes a crash via a failed assertion. Per QUIC specification, this particular message should be treated as a connection error. This issue affects mvfst versions prior to commit a67083ff4b8dcbb7ee2839da6338032030d712b0 and proxygen versions prior to v2021.03.15.00. Un paquete de escenario death es posible en mvfst por medio de un mensaje especialmente diseñado durante una sesión QUIC, lo que causa un bloqueo por medio de un fallo de aserción. Según la especificación QUIC, este mensaje en particular debe tratarse como un error de conexión. • https://github.com/facebookincubator/mvfst/commit/a67083ff4b8dcbb7ee2839da6338032030d712b0 https://www.facebook.com/security/advisories/cve-2021-24029 • CWE-617: Reachable Assertion •
CVE-2020-1897
https://notcve.org/view.php?id=CVE-2020-1897
A use-after-free is possible due to an error in lifetime management in the request adaptor when a malicious client invokes request error handling in a specific sequence. This issue affects versions of proxygen prior to v2020.05.18.00. Un uso de la memoria previamente liberada es posible debido a un error en la administración perpetua en el adaptador de petición cuando un cliente malicioso invoca el manejo de errores de petición en una secuencia específica. Este problema afecta a las versiones de proxygen anteriores a v2020.05.18.00. • https://www.facebook.com/security/advisories/cve-2020-1897 • CWE-416: Use After Free •
CVE-2019-11921
https://notcve.org/view.php?id=CVE-2019-11921
An out of bounds write is possible via a specially crafted packet in certain configurations of Proxygen due to improper handling of Base64 when parsing malformed binary content in Structured HTTP Headers. This issue affects versions of proxygen prior to v2019.07.22.00. Una escritura fuera de límites es posible a través de un paquete especialmente diseñado en ciertas configuraciones de Proxygen debido al manejo inadecuado de Base64 cuando se analiza contenido binario mal formado en Structured HTTP Headers. Este problema afecta a las versiones de proxygen anteriores a v2019.07.22.00. • https://github.com/facebook/proxygen/commit/2f07985bef9fbae124cc63e5c0272e32da4fdaec https://www.facebook.com/security/advisories/cve-2019-11921 • CWE-787: Out-of-bounds Write •
CVE-2018-6343
https://notcve.org/view.php?id=CVE-2018-6343
Proxygen fails to validate that a secondary auth manager is set before dereferencing it. That can cause a denial of service issue when parsing a Certificate/CertificateRequest HTTP2 Frame over a fizz (TLS 1.3) transport. This issue affects Proxygen releases starting from v2018.10.29.00 until the fix in v2018.11.19.00. Proxygen no logra validar que un gestor de autenticación secundario sea fijado antes de desreferenciarse. Esto podría provocar una denegación de servicio (DoS) cuando se analiza un frame HTTP2 "Certificate/CertificateRequest" sobre un transporte del tipo fizz (TLS 1.3). • https://github.com/facebook/proxygen/commit/0600ebe59c3e82cd012def77ca9ca1918da74a71 • CWE-20: Improper Input Validation CWE-476: NULL Pointer Dereference •