<html>
<head>
<base href="https://bugzilla.rosalinux.ru/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Platform</th>
<td>2021.1
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_CONFIRMED "
title="CONFIRMED - [CVE 21] undertow 1.4.0 CVEs found"
href="https://bugzilla.rosalinux.ru/show_bug.cgi?id=13336">13336</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[CVE 21] undertow 1.4.0 CVEs found
</td>
</tr>
<tr>
<th>Classification</th>
<td>ROSA-based products
</td>
</tr>
<tr>
<th>Product</th>
<td>ROSA Fresh
</td>
</tr>
<tr>
<th>Version</th>
<td>All
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>URL</th>
<td>CVE-2017-12165, CVE-2017-7559, CVE-2018-1067, CVE-2019-10184, CVE-2019-10212, CVE-2019-19343, CVE-2019-3888, CVE-2020-10687, CVE-2020-10705, CVE-2020-10719, CVE-2020-1757, CVE-2021-20220, CVE-2021-3597, CVE-2021-3629, CVE-2021-3690, CVE-2021-3859, CVE-2022-1319, CVE-2022-2053,
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux
</td>
</tr>
<tr>
<th>Status</th>
<td>CONFIRMED
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>Normal
</td>
</tr>
<tr>
<th>Component</th>
<td>System (kernel, glibc, systemd, bash, PAM...)
</td>
</tr>
<tr>
<th>Assignee</th>
<td>bugs@lists.rosalinux.ru
</td>
</tr>
<tr>
<th>Reporter</th>
<td>y.tumanov@rosalinux.ru
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>bugs@lists.rosalinux.ru
</td>
</tr>
<tr>
<th>CC</th>
<td>s.matveev@rosalinux.ru, y.tumanov@rosalinux.ru
</td>
</tr>
<tr>
<th>Target Milestone</th>
<td>---
</td>
</tr>
<tr>
<th>Flags</th>
<td>secteam_verified?
</td>
</tr></table>
<p>
<div>
<pre>Please patch CVEs for package undertow version 1.4.0
INFO (CVEs are): undertow 1.4.0
cves found
CVE-2017-12165
Desc: It was discovered that Undertow before 1.4.17, 1.3.31 and 2.0.0 processes
http request headers with unusual whitespaces which can cause possible http
request smuggling.
Link: <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-12165">https://nvd.nist.gov/vuln/detail/CVE-2017-12165</a>
Severity: HIGH
CVE-2017-7559
Desc: In Undertow 2.x before 2.0.0.Alpha2, 1.4.x before 1.4.17.Final, and 1.3.x
before 1.3.31.Final, it was found that the fix for CVE-2017-2666 was incomplete
and invalid characters are still allowed in the query string and path
parameters. This could be exploited, in conjunction with a proxy that also
permitted the invalid characters but with a different interpretation, to inject
data into the HTTP response. By manipulating the HTTP response the attacker
could poison a web-cache, perform an XSS attack, or obtain sensitive
information from requests other than their own.
Link: <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-7559">https://nvd.nist.gov/vuln/detail/CVE-2017-7559</a>
Severity: MEDIUM
CVE-2018-1067
Desc: In Undertow before versions 7.1.2.CR1, 7.1.2.GA it was found that the fix
for CVE-2016-4993 was incomplete and Undertow web server is vulnerable to the
injection of arbitrary HTTP headers, and also response splitting, due to
insufficient sanitization and validation of user input before the input is used
as part of an HTTP header value.
Link: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-1067">https://nvd.nist.gov/vuln/detail/CVE-2018-1067</a>
Severity: MEDIUM
CVE-2019-10184
Desc: undertow before version 2.0.23.Final is vulnerable to an information leak
issue. Web apps may have their directory structures predicted through requests
without trailing slashes via the api.
Link: <a href="https://nvd.nist.gov/vuln/detail/CVE-2019-10184">https://nvd.nist.gov/vuln/detail/CVE-2019-10184</a>
Severity: HIGH
CVE-2019-10212
Desc: A flaw was found in, all under 2.0.20, in the Undertow DEBUG log for
io.undertow.request.security. If enabled, an attacker could abuse this flaw to
obtain the user's credentials from the log files.
Link: <a href="https://nvd.nist.gov/vuln/detail/CVE-2019-10212">https://nvd.nist.gov/vuln/detail/CVE-2019-10212</a>
Severity: CRITICAL
CVE-2019-19343
Desc: A flaw was found in Undertow when using Remoting as shipped in Red Hat
Jboss EAP before version 7.2.4. A memory leak in HttpOpenListener due to
holding remote connections indefinitely may lead to denial of service. Versions
before undertow 2.0.25.SP1 and jboss-remoting 5.0.14.SP1 are believed to be
vulnerable.
Link: <a href="https://nvd.nist.gov/vuln/detail/CVE-2019-19343">https://nvd.nist.gov/vuln/detail/CVE-2019-19343</a>
Severity: HIGH
CVE-2019-3888
Desc: A vulnerability was found in Undertow web server before 2.0.21. An
information exposure of plain text credentials through log files because
Connectors.executeRootHandler:402 logs the HttpServerExchange object at ERROR
level using UndertowLogger.REQUEST_LOGGER.undertowRequestFailed(t, exchange)
Link: <a href="https://nvd.nist.gov/vuln/detail/CVE-2019-3888">https://nvd.nist.gov/vuln/detail/CVE-2019-3888</a>
Severity: CRITICAL
CVE-2020-10687
Desc: A flaw was discovered in all versions of Undertow before Undertow
2.2.0.Final, where HTTP request smuggling related to CVE-2017-2666 is possible
against HTTP/1.x and HTTP/2 due to permitting invalid characters in an HTTP
request. This flaw allows an attacker to poison a web-cache, perform an XSS
attack, or obtain sensitive information from request other than their own.
Link: <a href="https://nvd.nist.gov/vuln/detail/CVE-2020-10687">https://nvd.nist.gov/vuln/detail/CVE-2020-10687</a>
Severity: MEDIUM
CVE-2020-10705
Desc: A flaw was discovered in Undertow in versions before Undertow 2.1.1.Final
where certain requests to the "Expect: 100-continue" header may cause an out of
memory error. This flaw may potentially lead to a denial of service.
Link: <a href="https://nvd.nist.gov/vuln/detail/CVE-2020-10705">https://nvd.nist.gov/vuln/detail/CVE-2020-10705</a>
Severity: HIGH
CVE-2020-10719
Desc: A flaw was found in Undertow in versions before 2.1.1.Final, regarding
the processing of invalid HTTP requests with large chunk sizes. This flaw
allows an attacker to take advantage of HTTP request smuggling.
Link: <a href="https://nvd.nist.gov/vuln/detail/CVE-2020-10719">https://nvd.nist.gov/vuln/detail/CVE-2020-10719</a>
Severity: MEDIUM
CVE-2020-1757
Desc: A flaw was found in all undertow-2.x.x SP1 versions prior to
undertow-2.0.30.SP1, all undertow-1.x.x and undertow-2.x.x versions prior to
undertow-2.1.0.Final, where the Servlet container causes servletPath to
normalize incorrectly by truncating the path after semicolon which may lead to
an application mapping resulting in the security bypass.
Link: <a href="https://nvd.nist.gov/vuln/detail/CVE-2020-1757">https://nvd.nist.gov/vuln/detail/CVE-2020-1757</a>
Severity: HIGH
CVE-2021-20220
Desc: A flaw was found in Undertow. A regression in the fix for CVE-2020-10687
was found. HTTP request smuggling related to CVE-2017-2666 is possible against
HTTP/1.x and HTTP/2 due to permitting invalid characters in an HTTP request.
This flaw allows an attacker to poison a web-cache, perform an XSS attack, or
obtain sensitive information from request other than their own. The highest
threat from this vulnerability is to data confidentiality and integrity.
Link: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-20220">https://nvd.nist.gov/vuln/detail/CVE-2021-20220</a>
Severity: MEDIUM
CVE-2021-3597
Desc: A flaw was found in undertow. The HTTP2SourceChannel fails to write the
final frame under some circumstances, resulting in a denial of service. The
highest threat from this vulnerability is availability. This flaw affects
Undertow versions prior to 2.0.35.SP1, prior to 2.2.6.SP1, prior to 2.2.7.SP1,
prior to 2.0.36.SP1, prior to 2.2.9.Final and prior to 2.0.39.Final.
Link: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-3597">https://nvd.nist.gov/vuln/detail/CVE-2021-3597</a>
Severity: MEDIUM
CVE-2021-3629
Desc: A flaw was found in Undertow. A potential security issue in flow control
handling by the browser over http/2 may potentially cause overhead or a denial
of service in the server. The highest threat from this vulnerability is
availability. This flaw affects Undertow versions prior to 2.0.40.Final and
prior to 2.2.11.Final.
Link: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-3629">https://nvd.nist.gov/vuln/detail/CVE-2021-3629</a>
Severity: MEDIUM
CVE-2021-3690
Desc: A flaw was found in Undertow. A buffer leak on the incoming WebSocket
PONG message may lead to memory exhaustion. This flaw allows an attacker to
cause a denial of service. The highest threat from this vulnerability is
availability.
Link: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-3690">https://nvd.nist.gov/vuln/detail/CVE-2021-3690</a>
Severity: HIGH
CVE-2021-3859
Desc: A flaw was found in Undertow that tripped the client-side invocation
timeout with certain calls made over HTTP2. This flaw allows an attacker to
carry out denial of service attacks.
Link: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-3859">https://nvd.nist.gov/vuln/detail/CVE-2021-3859</a>
Severity: HIGH
CVE-2022-1319
Desc: A flaw was found in Undertow. For an AJP 400 response, EAP 7 is
improperly sending two response packets, and those packets have the reuse flag
set even though JBoss EAP closes the connection. A failure occurs when the
connection is reused after a 400 by CPING since it reads in the second
SEND_HEADERS response packet instead of a CPONG.
Link: <a href="https://nvd.nist.gov/vuln/detail/CVE-2022-1319">https://nvd.nist.gov/vuln/detail/CVE-2022-1319</a>
Severity: HIGH
CVE-2022-2053
Desc: When a POST request comes through AJP and the request exceeds the
max-post-size limit (maxEntitySize), Undertow's AjpServerRequestConduit
implementation closes a connection without sending any response to the
client/proxy. This behavior results in that a front-end proxy marking the
backend worker (application server) as an error state and not forward requests
to the worker for a while. In mod_cluster, this continues until the next STATUS
request (10 seconds intervals) from the application server updates the server
state. So, in the worst case, it can result in "All workers are in error state"
and mod_cluster responds "503 Service Unavailable" for a while (up to 10
seconds). In mod_proxy_balancer, it does not forward requests to the worker
until the "retry" timeout passes. However, luckily, mod_proxy_balancer has
"forcerecovery" setting (On by default; this parameter can force the immediate
recovery of all workers without considering the retry parameter of the workers
if all workers of a balancer are in error state.). So, unlike mod_cluster,
mod_proxy_balancer does not result in responding "503 Service Unavailable". An
attacker could use this behavior to send a malicious request and trigger server
errors, resulting in DoS (denial of service). This flaw was fixed in Undertow
2.2.19.Final, Undertow 2.3.0.Alpha2.
Link: <a href="https://nvd.nist.gov/vuln/detail/CVE-2022-2053">https://nvd.nist.gov/vuln/detail/CVE-2022-2053</a>
Severity: HIGH</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>