Bug 1802540 (CVE-2020-8661) - CVE-2020-8661 envoy: Response flooding for HTTP/1.1
Summary: CVE-2020-8661 envoy: Response flooding for HTTP/1.1
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2020-8661
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1802569
TreeView+ depends on / blocked
 
Reported: 2020-02-13 11:32 UTC by Dhananjay Arunesh
Modified: 2021-02-16 20:34 UTC (History)
3 users (show)

Fixed In Version: envoy 1.13.1
Doc Type: If docs needed, set a value
Doc Text:
A resource consumption vulnerability was found in the servicemesh-proxy in Envoy. An attacker could use pipelined requests to cause excessive amounts of memory to be used, possibly degrading or crashing the application.
Clone Of:
Environment:
Last Closed: 2020-03-05 22:31:45 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:0734 0 None None None 2020-03-05 19:00:19 UTC

Description Dhananjay Arunesh 2020-02-13 11:32:21 UTC 
A vulnerability was found in Envoy version 1.13.0 or earlier may consume excessive amounts of memory when responding internally to pipelined requests.
Comment 3 Mark Cooper 2020-02-24 04:39:25 UTC 
Acknowledgments:

Name: The Envoy Security Team
Comment 4 errata-xmlrpc 2020-03-05 19:00:18 UTC 
This issue has been addressed in the following products:

  OpenShift Service Mesh 1.0

Via RHSA-2020:0734 https://access.redhat.com/errata/RHSA-2020:0734
Comment 5 Product Security DevOps Team 2020-03-05 22:31:45 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-2020-8661
Comment 6 Mark Cooper 2020-03-08 22:19:35 UTC 
External References:

https://github.com/envoyproxy/envoy/security/advisories/GHSA-36cq-ww7h-p4j7
Note You need to log in before you can comment on or make changes to this bug.