CVSS: 6.7EPSS: 0%CPEs: 3EXPL: 0CVE-2023-41337 – h2o vulnerable to TLS session resumption misdirection
https://notcve.org/view.php?id=CVE-2023-41337
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 client trying to resume a TLS connection and an attacker redirecting the packets to a different address or port than that intended by the client. The attacker must already have been configured by the administrator of h2o to act as a backend to one of the addresses or ports that the h2o instance listens to. Session IDs and tickets generated by h2o are not bound to information specific to the server address, port, or the X.509 certificate, and therefore it is possible for an attacker to force the victim connection to wrongfully resume against a different server address or port on which the same h2o instance is listening. Once a TLS session is misdirected to resume to a server address / port that is configured to use an attacker-controlled server as the backend, depending on the configuration, HTTPS requests from the victim client may be forwarded to the attacker's server. An H2O instance is vulnerable to this attack only if the instance is configured to listen to different addresses or ports using the listen directive at the host level and the instance is configured to connect to backend servers managed by multiple entities. A patch is available at commit 35760540337a47e5150da0f4a66a609fad2ef0ab. As a workaround, one may stop using using host-level listen directives in favor of global-level ones. h2o es un servidor HTTP compatible con HTTP/1.x, HTTP/2 y HTTP/3. • https://github.com/h2o/h2o/commit/35760540337a47e5150da0f4a66a609fad2ef0ab https://github.com/h2o/h2o/security/advisories/GHSA-5v5r-rghf-rm6q • CWE-347: Improper Verification of Cryptographic Signature •
CVSS: 7.5EPSS: 83%CPEs: 444EXPL: 7CVE-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 •
CVSS: 8.2EPSS: 0%CPEs: 3EXPL: 0CVE-2023-30847 – H2O vulnerable to read from uninitialized pointer in the reverse proxy handler
https://notcve.org/view.php?id=CVE-2023-30847
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 https://github.com/h2o/h2o/pull/3229 https://github.com/h2o/h2o/security/advisories/GHSA-p5hj-phwj-hrvx • CWE-824: Access of Uninitialized Pointer •
CVSS: 7.4EPSS: 0%CPEs: 1EXPL: 0CVE-2021-43848 – Unititialized memory access in h2o
https://notcve.org/view.php?id=CVE-2021-43848
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 reflects the traffic sent from the client, an attacker can use that reflector to obtain internal state of h2o. • https://github.com/h2o/h2o/commit/8c0eca3 https://github.com/h2o/h2o/security/advisories/GHSA-f9xw-j925-m4m4 • CWE-908: Use of Uninitialized Resource •
CVSS: 9.8EPSS: 3%CPEs: 1EXPL: 0CVE-2018-0608
https://notcve.org/view.php?id=CVE-2018-0608
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 https://github.com/h2o/h2o/issues/1775 • CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer •