CVSS: 7.8EPSS: 0%CPEs: 4EXPL: 1CVE-2024-32974 – Envoy affected by a crash in EnvoyQuicServerStream::OnInitialHeadersComplete()
https://notcve.org/view.php?id=CVE-2024-32974
04 Jun 2024 — Envoy is a cloud-native, open source edge and service proxy. A crash was observed in `EnvoyQuicServerStream::OnInitialHeadersComplete()` with following call stack. It is a use-after-free caused by QUICHE continuing push request headers after `StopReading()` being called on the stream. As after `StopReading()`, the HCM's `ActiveStream` might have already be destroyed and any up calls from QUICHE could potentially cause use after free. Envoy es un proxy de servicio y borde de código abierto, nativo de la nube... • https://github.com/envoyproxy/envoy/security/advisories/GHSA-mgxp-7hhp-8299 • CWE-416: Use After Free •
CVSS: 7.8EPSS: 0%CPEs: 4EXPL: 1CVE-2024-32975 – Envoy crashes in QuicheDataReader::PeekVarInt62Length()
https://notcve.org/view.php?id=CVE-2024-32975
04 Jun 2024 — Envoy is a cloud-native, open source edge and service proxy. There is a crash at `QuicheDataReader::PeekVarInt62Length()`. It is caused by integer underflow in the `QuicStreamSequencerBuffer::PeekRegion()` implementation. Envoy es un proxy de servicio y borde de código abierto, nativo de la nube. Hay un bloqueo en `QuicheDataReader::PeekVarInt62Length()`. • https://github.com/envoyproxy/envoy/security/advisories/GHSA-g9mq-6v96-cpqc • CWE-191: Integer Underflow (Wrap or Wraparound) •
CVSS: 7.8EPSS: 0%CPEs: 4EXPL: 1CVE-2024-32976 – Envoy can enter an endless loop while decompressing Brotli data with extra input
https://notcve.org/view.php?id=CVE-2024-32976
04 Jun 2024 — Envoy is a cloud-native, open source edge and service proxy. Envoyproxy with a Brotli filter can get into an endless loop during decompression of Brotli data with extra input. Envoy es un proxy de servicio y borde de código abierto, nativo de la nube. Envoyproxy con un filtro Brotli puede entrar en un bucle sin fin durante la descompresión de datos Brotli con entrada adicional. A flaw was found in Envoy's Brotli decompressor. • https://github.com/envoyproxy/envoy/security/advisories/GHSA-7wp5-c2vq-4f8m • CWE-400: Uncontrolled Resource Consumption CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') •
CVSS: 5.9EPSS: 0%CPEs: 4EXPL: 1CVE-2024-34362 – Envoy affected by a crash (use-after-free) in EnvoyQuicServerStream
https://notcve.org/view.php?id=CVE-2024-34362
04 Jun 2024 — Envoy is a cloud-native, open source edge and service proxy. There is a use-after-free in `HttpConnectionManager` (HCM) with `EnvoyQuicServerStream` that can crash Envoy. An attacker can exploit this vulnerability by sending a request without `FIN`, then a `RESET_STREAM` frame, and then after receiving the response, closing the connection. Envoy es un proxy de servicio y borde de código abierto, nativo de la nube. Hay un use-after-free en `HttpConnectionManager` (HCM) con `EnvoyQuicServerStream` que puede b... • https://github.com/envoyproxy/envoy/security/advisories/GHSA-hww5-43gv-35jv • CWE-416: Use After Free •
CVSS: 7.8EPSS: 0%CPEs: 3EXPL: 1CVE-2024-34363 – Envoy can crash due to uncaught nlohmann JSON exception
https://notcve.org/view.php?id=CVE-2024-34363
04 Jun 2024 — Envoy is a cloud-native, open source edge and service proxy. Due to how Envoy invoked the nlohmann JSON library, the library could throw an uncaught exception from downstream data if incomplete UTF-8 strings were serialized. The uncaught exception would cause Envoy to crash. Envoy es un proxy de servicio y borde de código abierto, nativo de la nube. Debido a cómo Envoy invocó la librería JSON de nlohmann, la librería podría generar una excepción no detectada de los datos posteriores si se serializaran caden... • https://github.com/envoyproxy/envoy/security/advisories/GHSA-g979-ph9j-5gg4 • CWE-248: Uncaught Exception •
CVSS: 6.8EPSS: 0%CPEs: 4EXPL: 1CVE-2024-34364 – Envoy OOM vector from HTTP async client with unbounded response buffer for mirror response
https://notcve.org/view.php?id=CVE-2024-34364
04 Jun 2024 — Envoy is a cloud-native, open source edge and service proxy. Envoy exposed an out-of-memory (OOM) vector from the mirror response, since async HTTP client will buffer the response with an unbounded buffer. Envoy es un proxy de servicio y borde de código abierto, nativo de la nube. Envoy expuso un vector de falta de memoria (OOM) de la respuesta reflejada, ya que el cliente HTTP asíncrono almacenará la respuesta en un búfer ilimitado. • https://github.com/envoyproxy/envoy/security/advisories/GHSA-xcj3-h7vf-fw26 • CWE-400: Uncontrolled Resource Consumption CWE-787: Out-of-bounds Write •
CVSS: 8.5EPSS: 0%CPEs: 4EXPL: 0CVE-2024-23326 – Envoy incorrectly accepts HTTP 200 response for entering upgrade mode
https://notcve.org/view.php?id=CVE-2024-23326
04 Jun 2024 — Envoy is a cloud-native, open source edge and service proxy. A theoretical request smuggling vulnerability exists through Envoy if a server can be tricked into adding an upgrade header into a response. Per RFC https://www.rfc-editor.org/rfc/rfc7230#section-6.7 a server sends 101 when switching protocols. Envoy incorrectly accepts a 200 response from a server when requesting a protocol upgrade, but 200 does not indicate protocol switch. This opens up the possibility of request smuggling through Envoy if the ... • https://github.com/envoyproxy/envoy/security/advisories/GHSA-vcf8-7238-v74c • CWE-391: Unchecked Error Condition CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') •
CVSS: 7.5EPSS: 0%CPEs: 4EXPL: 0CVE-2024-32475 – Envoy RELEASE_ASSERT using auto_sni with :authority header > 255 bytes
https://notcve.org/view.php?id=CVE-2024-32475
18 Apr 2024 — Envoy is a cloud-native, open source edge and service proxy. When an upstream TLS cluster is used with `auto_sni` enabled, a request containing a `host`/`:authority` header longer than 255 characters triggers an abnormal termination of Envoy process. Envoy does not gracefully handle an error when setting SNI for outbound TLS connection. The error can occur when Envoy attempts to use the `host`/`:authority` header value longer than 255 characters as SNI for outbound TLS connection. SNI length is limited to 2... • https://github.com/envoyproxy/envoy/commit/b47fc6648d7c2dfe0093a601d44cb704b7bad382 • CWE-253: Incorrect Check of Function Return Value CWE-617: Reachable Assertion •
CVSS: 5.3EPSS: 84%CPEs: 4EXPL: 2CVE-2024-30255 – HTTP/2: CPU exhaustion due to CONTINUATION frame flood
https://notcve.org/view.php?id=CVE-2024-30255
04 Apr 2024 — Envoy is a cloud-native, open source edge and service proxy. The HTTP/2 protocol stack in Envoy versions prior to 1.29.3, 1.28.2, 1.27.4, and 1.26.8 are vulnerable to CPU exhaustion due to flood of CONTINUATION frames. Envoy's HTTP/2 codec allows the client to send an unlimited number of CONTINUATION frames even after exceeding Envoy's header map limits. This allows an attacker to send a sequence of CONTINUATION frames without the END_HEADERS bit set causing CPU utilization, consuming approximately 1 core p... • https://github.com/lockness-Ko/CVE-2024-27316 • CWE-390: Detection of Error Condition Without Action •
CVSS: 7.5EPSS: 14%CPEs: 1EXPL: 1CVE-2024-27919 – HTTP/2: memory exhaustion due to CONTINUATION frame flood
https://notcve.org/view.php?id=CVE-2024-27919
04 Apr 2024 — Envoy is a cloud-native, open-source edge and service proxy. In versions 1.29.0 and 1.29.1, theEnvoy HTTP/2 protocol stack is vulnerable to the flood of CONTINUATION frames. Envoy's HTTP/2 codec does not reset a request when header map limits have been exceeded. This allows an attacker to send an sequence of CONTINUATION frames without the END_HEADERS bit set causing unlimited memory consumption. This can lead to denial of service through memory exhaustion. • https://github.com/lockness-Ko/CVE-2024-27316 • CWE-390: Detection of Error Condition Without Action •