Bug 1945714 (CVE-2021-28165)

Summary: CVE-2021-28165 jetty: Resource exhaustion when receiving an invalid large TLS frame
Product: [Other] Security Response Reporter: Pedro Sampaio <psampaio>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: abenaiss, aileenc, aos-bugs, ataylor, bibryam, bmontgom, chazlett, dbecker, drieden, eclipse-sig, eparis, eric.wittmann, ggaughan, gmalinko, hbraun, janstey, java-maint, jburrell, jjohnstn, jjoyce, jnethert, jochrist, jokerman, jross, jschluet, jwon, krzysztof.daniel, lhh, lpeer, mburns, mizdebsk, mkolesni, nstielau, pantinor, pbhattac, sclewis, scohen, sd-operator-metering, slinaber, sochotni, sponnaga, swoodman, tflannag, vbobade
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: jetty 9.4.39, jetty 10.0.2, jetty 11.0.2 Doc Type: If docs needed, set a value
Doc Text:
When using SSL/TLS with Jetty, either with HTTP/1.1, HTTP/2, or WebSocket, the server may receive an invalid large (greater than 17408) TLS frame that is incorrectly handled, causing high CPU resources utilization. The highest threat from this vulnerability is to service availability.
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-06 20:34:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1945715, 1947810, 1947811, 1952068, 1952069, 1972366, 1987180    
Bug Blocks: 1945716    

Description Pedro Sampaio 2021-04-01 17:50:47 UTC
In Eclipse Jetty 7.2.2 to 9.4.38, 10.0.0.alpha0 to 10.0.1, and 11.0.0.alpha0 to 11.0.1, CPU usage can reach 100% upon receiving a large invalid TLS frame.

References:

https://github.com/eclipse/jetty.project/security/advisories/GHSA-26vr-8j45-3r4w

Comment 1 Pedro Sampaio 2021-04-01 17:51:33 UTC
Created jetty tracking bugs for this issue:

Affects: fedora-all [bug 1945715]

Comment 2 Przemyslaw Roguski 2021-04-08 11:09:24 UTC
External References:

https://github.com/eclipse/jetty.project/security/advisories/GHSA-26vr-8j45-3r4w

Comment 8 Anten Skrabec 2021-04-14 02:35:28 UTC
Statement:

In OpenShift Container Platform (OCP), the hive/presto/hadoop components that comprise the OCP metering stack, ship the vulnerable version of jetty.
Since the release of OCP 4.6, the metering product has been deprecated [1], hence the affected components are marked as wontfix.
This may be fixed in the future.

[1] https://docs.openshift.com/container-platform/4.6/release_notes/ocp-4-6-release-notes.html#ocp-4-6-metering-operator-deprecated

Red Hat OpenStack Platform's OpenDaylight will not be updated for this flaw because it was deprecated as of OpenStack Platform 14 and is only receiving security fixes for Important and Critical flaws.

Comment 9 Jonathan Christison 2021-04-19 10:14:16 UTC
This vulnerability is out of security support scope for the following products:
 * Red Hat JBoss Fuse 6
 * Red Hat JBoss A-MQ 6

Please refer to https://access.redhat.com/support/policy/updates/jboss_notes for more details.

Comment 10 Jonathan Christison 2021-04-21 10:55:28 UTC
Marking Red Hat Camel K as having a low impact, although Camel K distributes jetty artifacts through camel-jetty, camel-jetty itself is not available for use by the application developer, http functionality is provided by camel-k default runtime, Quarkus.

Comment 17 errata-xmlrpc 2021-05-05 13:26:58 UTC
This issue has been addressed in the following products:

  Red Hat Developer Tools

Via RHSA-2021:1509 https://access.redhat.com/errata/RHSA-2021:1509

Comment 18 Product Security DevOps Team 2021-05-06 20:34:09 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2021-28165

Comment 19 errata-xmlrpc 2021-05-13 15:16:10 UTC
This issue has been addressed in the following products:

  Red Hat AMQ Streams 1.6.4

Via RHSA-2021:1560 https://access.redhat.com/errata/RHSA-2021:1560

Comment 20 errata-xmlrpc 2021-05-19 15:01:07 UTC
This issue has been addressed in the following products:

  Red Hat OpenShift Container Platform 4.7

Via RHSA-2021:1551 https://access.redhat.com/errata/RHSA-2021:1551

Comment 23 errata-xmlrpc 2021-07-12 12:13:11 UTC
This issue has been addressed in the following products:

  Red Hat AMQ 7.8.2

Via RHSA-2021:2689 https://access.redhat.com/errata/RHSA-2021:2689

Comment 24 errata-xmlrpc 2021-08-11 18:24:02 UTC
This issue has been addressed in the following products:

  Red Hat Fuse 7.9

Via RHSA-2021:3140 https://access.redhat.com/errata/RHSA-2021:3140

Comment 25 errata-xmlrpc 2021-08-19 07:18:38 UTC
This issue has been addressed in the following products:

  Red Hat AMQ Streams 1.8.0

Via RHSA-2021:3225 https://access.redhat.com/errata/RHSA-2021:3225

Comment 27 errata-xmlrpc 2021-09-30 09:58:08 UTC
This issue has been addressed in the following products:

  Red Hat AMQ 7.9.0

Via RHSA-2021:3700 https://access.redhat.com/errata/RHSA-2021:3700

Comment 29 errata-xmlrpc 2021-11-23 10:35:32 UTC
This issue has been addressed in the following products:

  Red Hat Integration

Via RHSA-2021:4767 https://access.redhat.com/errata/RHSA-2021:4767

Comment 30 errata-xmlrpc 2022-09-09 07:12:36 UTC
This issue has been addressed in the following products:

  RHAF Camel-K 1.8

Via RHSA-2022:6407 https://access.redhat.com/errata/RHSA-2022:6407