H2O vulnerabilities, page 3
47 vulnerabilities
Known vulnerabilities in H2O products, newest first, with CVSS severity, EPSS, KEV listings and ransomware use, across 3 products.
RoutineCVE-2023-41337h2o +3 moreh2o vulnerable to TLS session resumption misdirectionh2o 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.CVSS6.7MediumEPSS0.18%PrioritiseCVE-2023-6013h2oai · h2oai/h2o-3 +1 moreH2O Local File IncludeH2O is vulnerable to stored XSS vulnerability which can lead to a Local File Include attack.CVSS9.3CriticalEPSS0.75%PrioritiseCVE-2023-6017h2oai · h2oai/h2o-3 +1 moreH2O S3 Bucket TakeoverH2O included a reference to an S3 bucket that no longer existed allowing an attacker to take over the S3 bucket URL.CVSS8.7HighEPSS0.85%PrioritiseCVE-2023-6038h2oai · h2oai/h2o-3 +2 moreLocal File Inclusion in h2oai/h2o-3A Local File Inclusion (LFI) vulnerability exists in the h2o-3 REST API, allowing unauthenticated remote attackers to read arbitrary files on the server with the permissions of the user running the h2o-3 instance. This issue affects the default installation and does not require user interaction. The vulnerability can be exploited by making specific GET or POST requests to the ImportFiles and ParseSetup endpoints, respectively. This issue was identified in version 3.40.0.4 of h2o-3.CVSS9.3CriticalEPSS4.34%PrioritiseCVE-2023-6016h2oai · h2oai/h2o-3 +1 moreH2O Remote Code Execution via POJO Model ImportAn attacker is able to gain remote code execution on a server hosting the H2O dashboard through it's POJO model import feature.CVSS10.0CriticalEPSS30.57%PrioritiseCVE-2023-30847h2o +2 moreH2O vulnerable to read from uninitialized pointer in the reverse proxy handlerH2O 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. Users should upgrade to commit f010336 or later.CVSS8.2HighEPSS0.90%PrioritiseCVE-2021-43848h2o +2 moreUnititialized memory access in h2oh2o 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. This internal state includes traffic of other connections in unencrypted form and TLS session tickets. This vulnerability exists in h2o server with HTTP/3 support, between commit 93af138 and d1f0f65. None of the released versions of h2o are affected by this vulnerability. There are no known workarounds. Users of unreleased versions of h2o using HTTP/3 are advised to upgrade immediately.CVSS7.4HighEPSS2.67%