Bug 2217983 (CVE-2023-35945) - CVE-2023-35945 envoy: HTTP/2 memory leak in nghttp2 codec
Summary: CVE-2023-35945 envoy: HTTP/2 memory leak in nghttp2 codec
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2023-35945
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 2217969
TreeView+ depends on / blocked
 
Reported: 2023-06-27 18:40 UTC by Guilherme de Almeida Suckevicz
Modified: 2023-09-14 17:35 UTC (History)
11 users (show)

Fixed In Version: envoy 1.26.3, envoy 1.25.8, envoy 1.24.9, envoy 1.23.11
Clone Of:
Environment:
Last Closed: 2023-08-11 21:34:45 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2023:4624 0 None None None 2023-08-11 16:48:19 UTC
Red Hat Product Errata RHSA-2023:5175 0 None None None 2023-09-14 17:35:41 UTC

Description Guilherme de Almeida Suckevicz 2023-06-27 18:40:17 UTC
Specifically crafter response from an untrusted upstream service can cause the denial of service through memory exhaustion. This is caused by Envoy’s HTTP/2 codec may leak a header map and bookkeeping structures upon receiving RST_STREAM immediately followed by the GOAWAY frames from an upstream server.

Comment 5 errata-xmlrpc 2023-08-11 16:48:18 UTC
This issue has been addressed in the following products:

  Red Hat OpenShift Service Mesh 2.3 for RHEL 8

Via RHSA-2023:4624 https://access.redhat.com/errata/RHSA-2023:4624

Comment 6 Product Security DevOps Team 2023-08-11 21:34:43 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-2023-35945

Comment 7 errata-xmlrpc 2023-09-14 17:35:40 UTC
This issue has been addressed in the following products:

  Red Hat OpenShift Service Mesh 2.2 for RHEL 8

Via RHSA-2023:5175 https://access.redhat.com/errata/RHSA-2023:5175


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