h2o — security advisory
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 addr
- Products
- h2o
- Affected versions
- 2.2.5+dfsg2-10, 2.2.5+dfsg2-11, 2.2.5+dfsg2-7, 2.2.5+dfsg2-8, 2.2.5+dfsg2-8.1, 2.2.5+dfsg2-8.1~exp1, 2.2.5+dfsg2-9
- Fixed versions
- Not specified
- CVEs
- CVE-2023-41337
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 1 Nov 2026, 15:57 UTC · Revision 1
Source evidence
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 addr
osv:DEBIAN-CVE-2023-41337
h2o
Fixed versions: Not specified
Complete source record
{
"id": "d36290b7d4728247e4f337ec73d61cf58c790f1dab52ea2afb3dbf9d932ce641",
"url": "https://osv.dev/vulnerability/DEBIAN-CVE-2023-41337",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "DEBIAN-CVE-2023-41337",
"summary": "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 addr",
"evidence": "osv:DEBIAN-CVE-2023-41337",
"products": [
{
"name": {
"value": "h2o",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [],
"affected_versions": [
{
"value": "2.2.5+dfsg2-10",
"evidence": "/affected/0/versions"
},
{
"value": "2.2.5+dfsg2-11",
"evidence": "/affected/0/versions"
},
{
"value": "2.2.5+dfsg2-7",
"evidence": "/affected/0/versions"
},
{
"value": "2.2.5+dfsg2-8",
"evidence": "/affected/0/versions"
},
{
"value": "2.2.5+dfsg2-8.1",
"evidence": "/affected/0/versions"
},
{
"value": "2.2.5+dfsg2-8.1~exp1",
"evidence": "/affected/0/versions"
},
{
"value": "2.2.5+dfsg2-9",
"evidence": "/affected/0/versions"
}
]
}
],
"severity": "medium",
"structured": {
"id": "DEBIAN-CVE-2023-41337",
"aliases": [
"DEBIAN-CVE-2023-41337"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N"
}
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
}
]
}
],
"package": {
"name": "h2o",
"purl": "pkg:deb/debian/h2o?arch=source&distro=bookworm",
"ecosystem": "Debian:12"
},
"versions": [
"2.2.5+dfsg2-10",
"2.2.5+dfsg2-11",
"2.2.5+dfsg2-7",
"2.2.5+dfsg2-8",
"2.2.5+dfsg2-8.1",
"2.2.5+dfsg2-8.1~exp1",
"2.2.5+dfsg2-9"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2023-41337.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
}
],
"modified": "2026-10-26T18:02:32.454893386Z",
"provider": "osv",
"upstream": [
"CVE-2023-41337"
],
"references": [
"https://security-tracker.debian.org/tracker/CVE-2023-41337"
]
},
"related_cves": [
{
"value": "CVE-2023-41337",
"evidence": "/upstream"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 456210,
"published_at": "2023-12-12T20:15:07.477+00:00"
}