h2o - Debian Package Tracker

general

source: h2o (main)
version: 2.2.5+dfsg2-9
maintainer: Apollon Oikonomopoulos (DMD) (LowNMU)
uploaders: Anton Gladky [DMD]
arch: all any
std-ver: 4.7.0
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 2.2.5+dfsg2-2+deb10u1
o-o-sec: 2.2.5+dfsg2-2+deb10u2
oldstable: 2.2.5+dfsg2-6
stable: 2.2.5+dfsg2-7
testing: 2.2.5+dfsg2-9
unstable: 2.2.5+dfsg2-9

versioned links

2.2.5+dfsg2-2+deb10u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.2.5+dfsg2-2+deb10u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.2.5+dfsg2-6: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.2.5+dfsg2-7: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.2.5+dfsg2-9: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

h2o (2 bugs: 0, 2, 0, 0)
h2o-doc
libh2o-dev
libh2o-dev-common
libh2o-evloop-dev
libh2o-evloop0.13t64
libh2o0.13t64

action needed

Problems while searching for a new upstream version high

uscan had problems while searching for a new upstream version:

In debian/watch no matching files for watch line
  https://github.com/h2o/h2o/releases .*/archive/v(.*)\.tar\.gz

Created: 2021-03-23 Last update: 2024-11-08 22:01

The VCS repository is not up to date, push the missing commits. high

vcswatch reports that the current version of the package is not in its VCS.
Either you need to push your commits and/or your tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be modified in salsa.debian.org in the project's general settings with the "Default Branch" field). Alternatively the Vcs-Git field in debian/control can contain a "-b <branch-name>" suffix to indicate what branch is used for the Debian packaging.

Created: 2024-10-18 Last update: 2024-11-08 00:33

3 security issues in trixie high

There are 3 open security issues in trixie.

3 important issues:

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.
CVE-2024-25622: 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 as expected. Depending on the headers being added or removed unexpectedly, this behavior could lead to unexpected client behavior. This vulnerability is fixed in commit 123f5e2b65dcdba8f7ef659a00d24bd1249141be.
CVE-2024-45397: 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 addressed in commit 15ed15a. Users may disable the use of TCP FastOpen and QUIC to mitigate the issue.

Created: 2023-12-24 Last update: 2024-10-21 22:30

3 security issues in sid high

There are 3 open security issues in sid.

3 important issues:

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.
CVE-2024-25622: 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 as expected. Depending on the headers being added or removed unexpectedly, this behavior could lead to unexpected client behavior. This vulnerability is fixed in commit 123f5e2b65dcdba8f7ef659a00d24bd1249141be.
CVE-2024-45397: 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 addressed in commit 15ed15a. Users may disable the use of TCP FastOpen and QUIC to mitigate the issue.

Created: 2023-12-24 Last update: 2024-10-21 22:30

debian/patches: 1 patch with invalid metadata, 9 patches to forward upstream high

Among the 10 debian patches available in version 2.2.5+dfsg2-9 of the package, we noticed the following issues:

1 patch with invalid metadata that ought to be fixed.
9 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2024-10-18 20:34

1 security issue in buster high

There is 1 open security issue in buster.

1 important issue:

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.

Created: 2023-12-24 Last update: 2024-05-03 05:39

2 bugs tagged patch in the BTS normal

The BTS contains patches fixing 2 bugs, consider including or untagging them.

Created: 2024-02-25 Last update: 2024-11-09 01:30

Fails to build during reproducibility testing normal

A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!

Created: 2024-10-20 Last update: 2024-11-08 23:32

Multiarch hinter reports 1 issue(s) low

There are issues with the multiarch metadata for this package.

h2o-doc could be marked Multi-Arch: foreign

Created: 2017-09-21 Last update: 2024-11-08 22:31

4 low-priority security issues in bookworm low

There are 4 open security issues in bookworm.

4 issues left for the package maintainer to handle:

CVE-2023-41337: (needs triaging) 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.
CVE-2023-44487: (needs triaging) 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.
CVE-2024-25622: (needs triaging) 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 as expected. Depending on the headers being added or removed unexpectedly, this behavior could lead to unexpected client behavior. This vulnerability is fixed in commit 123f5e2b65dcdba8f7ef659a00d24bd1249141be.
CVE-2024-45397: (needs triaging) 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 addressed in commit 15ed15a. Users may disable the use of TCP FastOpen and QUIC to mitigate the issue.

You can find information about how to handle these issues in the security team's documentation.

Created: 2023-06-10 Last update: 2024-10-21 22:30

Build log checks report 1 warning low

Build log checks report 1 warning

Created: 2018-06-03 Last update: 2018-09-23 06:00

news

[rss feed]

[2024-10-20] h2o 2.2.5+dfsg2-9 MIGRATED to testing (Debian testing watch)
[2024-10-18] Accepted h2o 2.2.5+dfsg2-9 (source) into unstable (Anton Gladky)
[2024-08-10] h2o REMOVED from testing (Debian testing watch)
[2024-05-03] h2o 2.2.5+dfsg2-8.1 MIGRATED to testing (Debian testing watch)
[2024-02-28] Accepted h2o 2.2.5+dfsg2-8.1 (source) into unstable (Lukas Märdian)
[2024-02-01] Accepted h2o 2.2.5+dfsg2-8.1~exp1 (source) into experimental (Graham Inggs)
[2023-10-29] Accepted h2o 2.2.5+dfsg2-2+deb10u2 (source) into oldoldstable (Anton Gladky)
[2023-10-22] h2o 2.2.5+dfsg2-8 MIGRATED to testing (Debian testing watch)
[2023-10-22] h2o 2.2.5+dfsg2-8 MIGRATED to testing (Debian testing watch)
[2023-10-20] Accepted h2o 2.2.5+dfsg2-8 (source) into unstable (Anton Gladky)
[2023-04-11] h2o 2.2.5+dfsg2-7 MIGRATED to testing (Debian testing watch)
[2023-03-21] Accepted h2o 2.2.5+dfsg2-7 (source) into unstable (Chris Hofstaedtler) (signed by: Christian Hofstaedtler)
[2022-04-21] h2o 2.2.5+dfsg2-6.2 MIGRATED to testing (Debian testing watch)
[2022-04-19] Accepted h2o 2.2.5+dfsg2-6.2 (source) into unstable (Chris Hofstaedtler) (signed by: Christian Hofstaedtler)
[2021-10-19] h2o 2.2.5+dfsg2-6.1 MIGRATED to testing (Debian testing watch)
[2021-10-17] Accepted h2o 2.2.5+dfsg2-6.1 (source) into unstable (Chris Hofstaedtler) (signed by: Christian Hofstaedtler)
[2020-12-21] h2o 2.2.5+dfsg2-6 MIGRATED to testing (Debian testing watch)
[2020-12-16] Accepted h2o 2.2.5+dfsg2-6 (source) into unstable (Anton Gladky)
[2020-05-04] h2o 2.2.5+dfsg2-5 MIGRATED to testing (Debian testing watch)
[2020-05-02] Accepted h2o 2.2.5+dfsg2-5 (source) into unstable (Anton Gladky)
[2020-05-01] Accepted h2o 2.2.5+dfsg2-5~exp1 (source) into experimental (Anton Gladky)
[2020-04-28] Accepted h2o 2.2.5+dfsg2-4 (source) into unstable (Anton Gladky)
[2019-08-31] Accepted h2o 2.2.5+dfsg2-2+deb10u1 (source amd64 all) into proposed-updates->stable-new, proposed-updates (Anton Gladky)
[2019-08-25] Accepted h2o 2.2.5+dfsg2-3~bpo9+1 (source) into stretch-backports->backports-policy, stretch-backports (Anton Gladky)
[2019-08-24] Accepted h2o 2.2.5+dfsg2-2+deb10u1 (source amd64 all) into stable->embargoed, stable (Anton Gladky)
[2019-08-23] h2o 2.2.5+dfsg2-3 MIGRATED to testing (Debian testing watch)
[2019-08-20] Accepted h2o 2.2.5+dfsg2-3 (source) into unstable (Anton Gladky)
[2018-10-28] h2o 2.2.5+dfsg2-2 MIGRATED to testing (Debian testing watch)
[2018-10-09] h2o REMOVED from testing (Debian testing watch)
[2018-10-01] Accepted h2o 2.2.5+dfsg2-2 (source) into unstable (Anton Gladky)

bugs [bug history graph]

all: 8
RC: 0
I&N: 8
M&W: 0
F&P: 0
patch: 2

links

homepage
lintian
buildd: logs, checks, reproducibility, cross
popcon
browse source code
edit tags
other distros
security tracker
screenshots
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 2.2.5+dfsg2-8.1ubuntu3
2 bugs
patches for 2.2.5+dfsg2-8.1ubuntu3