Bug 2117506 (CVE-2022-2764) - CVE-2022-2764 Undertow: DoS can be achieved as Undertow server waits for the LAST_CHUNK forever for EJB invocations
Summary: CVE-2022-2764 Undertow: DoS can be achieved as Undertow server waits for the ...
Keywords:
Status: NEW
Alias: CVE-2022-2764
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 2117501
TreeView+ depends on / blocked
 
Reported: 2022-08-11 08:10 UTC by Sandipan Roy
Modified: 2022-11-14 23:22 UTC (History)
74 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in Undertow with EJB invocations. This flaw allows an attacker to generate a valid HTTP request and send it to the server on an established connection after removing the LAST_CHUNK from the bytes, causing a denial of service.
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Sandipan Roy 2022-08-11 08:10:56 UTC
UndertowInputStream.close() blocks waiting to read -1

https://issues.redhat.com/browse/UNDERTOW-2048

Comment 4 Peter Palaga 2022-08-29 15:42:15 UTC
@pjindal I see that this CVE is valid fro Undertow 2.x. I wonder whether it is also reproducible on quarkus-http which was developed on top of Undertow 2.x?
Note that there is io.undertow.httpcore.UndertowInputStream class in quarkus-http.

Comment 5 Paramvir jindal 2022-08-30 05:44:54 UTC
In reply to comment #4:
> @pjindal I see that this CVE is valid fro Undertow 2.x. I wonder
> whether it is also reproducible on quarkus-http which was developed on top
> of Undertow 2.x?
> Note that there is io.undertow.httpcore.UndertowInputStream class in
> quarkus-http.

Peter, I have added you in https://issues.redhat.com/browse/UNDERTOW-2048, there is a comment on this jira on details about reproducing this issue. Also since quarkus-http is based on Undertow 2.x means quarkus ships the affected code and hence it should be marked as affected. I am still not sure if this can be reproduced in quarkus as it is not easy to reproduce. 

Since this is already a Low impact CVE, I am marking quarkus as affected for this CVE so that we can fix the affected undertow code in quarkus 2.x.

Comment 10 james 2022-09-13 09:46:44 UTC
Is there a simple mitigation for this?

As far as I am aware, I don't use EJB invocations. Is there a setting to disable them, or are they not even configured by default?


Note You need to log in before you can comment on or make changes to this bug.