18 results (0.005 seconds)

CVSS: 3.7EPSS: 0%CPEs: 1EXPL: 0

11 Oct 2024 — h2o is an HTTP server with support for HTTP/1.x, HTTP/2 and HTTP/3. When h2o is configured as a reverse proxy and HTTP/3 requests are cancelled by the client, h2o might crash due to an assertion failure. The crash can be exploited by an attacker to mount a Denial-of-Service attack. By default, the h2o standalone server automatically restarts, minimizing the impact. However, HTTP requests that were served concurrently will still be disrupted. • https://github.com/h2o/h2o/commit/16b13eee8ad7895b4fe3fcbcabee53bd52782562 • CWE-617: Reachable Assertion •

CVSS: 5.9EPSS: 0%CPEs: 1EXPL: 0

11 Oct 2024 — h2o is an HTTP server with support for HTTP/1.x, HTTP/2 and HTTP/3. When an HTTP request using TLS/1.3 early data on top of TCP Fast Open or QUIC 0-RTT packets is received and the IP-address-based access control is used, the access control does not detect and prohibit HTTP requests conveyed by packets with a spoofed source address. This behavior allows attackers on the network to execute HTTP requests from addresses that are otherwise rejected by the address-based access control. The vulnerability has been ... • https://github.com/h2o/h2o/commit/15ed15a2efb83a77bb4baaa5a119e639c2f6898a • CWE-284: Improper Access Control •

CVSS: 3.1EPSS: 0%CPEs: 1EXPL: 0

11 Oct 2024 — h2o is an HTTP server with support for HTTP/1.x, HTTP/2 and HTTP/3. The configuration directives provided by the headers handler allows users to modify the response headers being sent by h2o. The configuration file of h2o has scopes, and the inner scopes (e.g., path level) are expected to inherit the configuration defined in outer scopes (e.g., global level). However, if a header directive is used in the inner scope, all the definition in outer scopes are ignored. This can lead to headers not being modified... • https://github.com/h2o/h2o/commit/123f5e2b65dcdba8f7ef659a00d24bd1249141be • CWE-670: Always-Incorrect Control Flow Implementation •

CVSS: 9.3EPSS: 0%CPEs: 1EXPL: 1

14 Dec 2023 — External Control of File Name or Path in h2oai/h2o-3 Control externo del nombre o ruta del archivo en h2oai/h2o-3 • https://huntr.com/bounties/a5d003dc-c23e-4c98-8dcf-35ba9252fa3c • CWE-73: External Control of File Name or Path CWE-610: Externally Controlled Reference to a Resource in Another Sphere •

CVSS: 7.8EPSS: 0%CPEs: 3EXPL: 0

12 Dec 2023 — h2o is an HTTP server with support for HTTP/1.x, HTTP/2 and HTTP/3. The QUIC stack (quicly), as used by H2O up to commit 43f86e5 (in version 2.3.0-beta and prior), is susceptible to a state exhaustion attack. When H2O is serving HTTP/3, a remote attacker can exploit this vulnerability to progressively increase the memory retained by the QUIC stack. This can eventually cause H2O to abort due to memory exhaustion. The vulnerability has been resolved in commit d67e81d03be12a9d53dc8271af6530f40164cd35. • https://github.com/h2o/h2o/commit/d67e81d03be12a9d53dc8271af6530f40164cd35 • CWE-770: Allocation of Resources Without Limits or Throttling •

CVSS: 7.1EPSS: 0%CPEs: 3EXPL: 0

12 Dec 2023 — h2o is an HTTP server with support for HTTP/1.x, HTTP/2 and HTTP/3. In version 2.3.0-beta2 and prior, when h2o is configured to listen to multiple addresses or ports with each of them using different backend servers managed by multiple entities, a malicious backend entity that also has the opportunity to observe or inject packets exchanged between the client and h2o may misdirect HTTPS requests going to other backends and observe the contents of that HTTPS request being sent. The attack involves a victim cl... • https://github.com/h2o/h2o/commit/35760540337a47e5150da0f4a66a609fad2ef0ab • CWE-347: Improper Verification of Cryptographic Signature •

CVSS: 7.8EPSS: 94%CPEs: 444EXPL: 17

10 Oct 2023 — 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. ... • https://github.com/imabee101/CVE-2023-44487 • CWE-400: Uncontrolled Resource Consumption •

CVSS: 8.5EPSS: 0%CPEs: 3EXPL: 0

27 Apr 2023 — H2O is an HTTP server. In versions 2.3.0-beta2 and prior, when the reverse proxy handler tries to processes a certain type of invalid HTTP request, it tries to build an upstream URL by reading from uninitialized pointer. This behavior can lead to crashes or leak of information to back end HTTP servers. Pull request number 3229 fixes the issue. The pull request has been merged to the `master` branch in commit f010336. • https://github.com/h2o/h2o/commit/f010336bab162839df43d9e87570897466c97e33 • CWE-824: Access of Uninitialized Pointer •

CVSS: 7.4EPSS: 12%CPEs: 1EXPL: 1

01 Feb 2022 — h2o is an open source http server. In code prior to the `8c0eca3` commit h2o may attempt to access uninitialized memory. When receiving QUIC frames in certain order, HTTP/3 server-side implementation of h2o can be misguided to treat uninitialized memory as HTTP/3 frames that have been received. When h2o is used as a reverse proxy, an attacker can abuse this vulnerability to send internal state of h2o to backend servers controlled by the attacker or third party. Also, if there is an HTTP endpoint that reflec... • https://github.com/neex/hui2ochko • CWE-908: Use of Uninitialized Resource •

CVSS: 9.8EPSS: 2%CPEs: 1EXPL: 0

26 Jun 2018 — Buffer overflow in H2O version 2.2.4 and earlier allows remote attackers to execute arbitrary code or cause a denial of service (DoS) via unspecified vectors. Desbordamiento de búfer en H2O, en versiones 2.2.4 y anteriores, permite que atacantes remotos ejecuten código arbitrario o provoquen una denegación de servicio (DoS) mediante vectores sin especificar. • http://jvn.jp/en/jp/JVN93226941/index.html • CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer •