jetty12 - Debian Package Tracker

general

source: jetty12 (main)
version: 12.0.17-3.1
maintainer: Debian Java Maintainers (archive) (DMD)
uploaders: Emmanuel Bourg [DMD]
arch: all
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]

stable: 12.0.17-3
testing: 12.0.17-3
unstable: 12.0.17-3.1

versioned links

12.0.17-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
12.0.17-3.1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

jetty12 (2 bugs: 0, 2, 0, 0)
libjetty12-extra-java
libjetty12-java

action needed

A new upstream version is available: 12.1.1 high

A new upstream version 12.1.1 is available, you should consider packaging it.

Created: 2025-04-13 Last update: 2025-09-10 13:33

1 security issue in trixie high

There is 1 open security issue in trixie.

1 important issue:

CVE-2025-5115: In Eclipse Jetty, versions <=9.4.57, <=10.0.25, <=11.0.25, <=12.0.21, <=12.1.0.alpha2, an HTTP/2 client may trigger the server to send RST_STREAM frames, for example by sending frames that are malformed or that should not be sent in a particular stream state, therefore forcing the server to consume resources such as CPU and memory. For example, a client can open a stream and then send WINDOW_UPDATE frames with window size increment of 0, which is illegal. Per specification https://www.rfc-editor.org/rfc/rfc9113.html#name-window_update , the server should send a RST_STREAM frame. The client can now open another stream and send another bad WINDOW_UPDATE, therefore causing the server to consume more resources than necessary, as this case does not exceed the max number of concurrent streams, yet the client is able to create an enormous amount of streams in a short period of time. The attack can be performed with other conditions (for example, a DATA frame for a closed stream) that cause the server to send a RST_STREAM frame. Links: * https://github.com/jetty/jetty.project/security/advisories/GHSA-mmxm-8w33-wc4h

Created: 2025-08-21 Last update: 2025-09-07 12:02

1 security issue in forky high

There is 1 open security issue in forky.

1 important issue:

CVE-2025-5115: In Eclipse Jetty, versions <=9.4.57, <=10.0.25, <=11.0.25, <=12.0.21, <=12.1.0.alpha2, an HTTP/2 client may trigger the server to send RST_STREAM frames, for example by sending frames that are malformed or that should not be sent in a particular stream state, therefore forcing the server to consume resources such as CPU and memory. For example, a client can open a stream and then send WINDOW_UPDATE frames with window size increment of 0, which is illegal. Per specification https://www.rfc-editor.org/rfc/rfc9113.html#name-window_update , the server should send a RST_STREAM frame. The client can now open another stream and send another bad WINDOW_UPDATE, therefore causing the server to consume more resources than necessary, as this case does not exceed the max number of concurrent streams, yet the client is able to create an enormous amount of streams in a short period of time. The attack can be performed with other conditions (for example, a DATA frame for a closed stream) that cause the server to send a RST_STREAM frame. Links: * https://github.com/jetty/jetty.project/security/advisories/GHSA-mmxm-8w33-wc4h

Created: 2025-08-21 Last update: 2025-09-07 12:02

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: 2025-09-07 Last update: 2025-09-07 10:35

Does not build reproducibly during 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: 2025-04-27 Last update: 2025-09-10 18:03

lintian reports 2 warnings normal

Lintian reports 2 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2025-09-07 Last update: 2025-09-07 15:03

1 open merge request in Salsa normal

There is 1 open merge request for this package on Salsa. You should consider reviewing and/or merging these merge requests.

Created: 2025-08-19 Last update: 2025-08-19 06:28

debian/patches: 1 patch to forward upstream low

Among the 7 debian patches available in version 12.0.17-3.1 of the package, we noticed the following issues:

1 patch 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: 2025-09-07 Last update: 2025-09-07 13:33

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.2 instead of 4.7.0).

Created: 2025-04-13 Last update: 2025-09-07 10:36

testing migrations

excuses:
- Migration status for jetty12 (12.0.17-3 to 12.0.17-3.1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- ∙ ∙ Too young, only 4 of 5 days old
- Additional info:
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jetty12.html
- ∙ ∙ Ignoring non-reproducibility on amd64 (not a regression) - info ♻
- ∙ ∙ Ignoring non-reproducibility on arm64 (not a regression) - info ♻
- Not considered

news

[rss feed]

[2025-09-07] Accepted jetty12 12.0.17-3.1 (source) into unstable (Adrian Bunk)
[2025-04-27] jetty12 12.0.17-3 MIGRATED to testing (Debian testing watch)
[2025-04-14] Accepted jetty12 12.0.17-3 (source) into unstable (Emmanuel Bourg)
[2025-04-13] Accepted jetty12 12.0.17-2 (source) into unstable (Emmanuel Bourg)
[2025-04-13] Accepted jetty12 12.0.17-1 (source all) into unstable (Debian FTP Masters) (signed by: Emmanuel Bourg)

bugs [bug history graph]

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

links

homepage
lintian (0, 2)
buildd: logs, reproducibility
popcon
browse source code
edit tags
other distros
security tracker
screenshots
debian patches