Your message dated Sun, 26 Oct 2025 20:46:03 +0100
with message-id <[email protected]>
and subject line Re: Bug#1077546: undertow: CVE-2024-6162
has caused the Debian Bug report #1077546,
regarding undertow: CVE-2024-6162
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1077546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077546
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: undertow
X-Debbugs-CC: [email protected]
Severity: important
Tags: security
Hi,
The following vulnerability was published for undertow.
CVE-2024-6162[0]:
| A vulnerability was found in Undertow. URL-encoded request path
| information can be broken for concurrent requests on ajp-listener,
| causing the wrong path to be processed and resulting in a possible
| denial of service.
https://bugzilla.redhat.com/show_bug.cgi?id=2293069
If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
For further information see:
[0] https://security-tracker.debian.org/tracker/CVE-2024-6162
https://www.cve.org/CVERecord?id=CVE-2024-6162
Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Version: 2.3.18-1
Hi tony,
you're right. This issue is fixed in 2.3.18-1. I'm going to close this issue
now.
https://github.com/undertow-io/undertow/pull/1609/commits/90f202ada89b6d9883beed0f1fe10c99d470d9a8
Markus
signature.asc
Description: This is a digitally signed message part
--- End Message ---
__
This is the maintainer address of Debian's Java team
<https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-java-maintainers>.
Please use
[email protected] for discussions and questions.
