CNCF Envoy up to 1.13.0 Pipeline Request resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in CNCF Envoy up to 1.13.0. Affected by this issue is some unknown functionality of the component Pipeline Handler. This manipulation as part of Request causes resource consumption. This vulnerability is tracked as CVE-2020-8661. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as problematic was found in CNCF Envoy up to 1.13.0. Affected by this vulnerability is some unknown processing of the component Pipeline Handler. The manipulation as part of a Request leads to a resource consumption vulnerability. The CWE definition for the vulnerability is CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. As an impact it is known to affect availability. The summary by CVE is:
CNCF Envoy through 1.13.0 may consume excessive amounts of memory when responding internally to pipelined requests.
The weakness was disclosed 03/04/2020 (Website). The advisory is shared at envoyproxy.io. This vulnerability is known as CVE-2020-8661 since 02/06/2020. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-150875, VDB-150876 and VDB-150878 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Resource consumptionCWE: CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
02/06/2020 🔍03/04/2020 🔍
03/05/2020 🔍
04/09/2024 🔍
Sources
Advisory: RHSA-2020:0734Status: Not defined
CVE: CVE-2020-8661 (🔍)
GCVE (CVE): GCVE-0-2020-8661
GCVE (VulDB): GCVE-100-150877
See also: 🔍
Entry
Created: 03/05/2020 08:29Updated: 04/09/2024 14:51
Changes: 03/05/2020 08:29 (39), 03/05/2020 08:34 (17), 04/09/2024 14:51 (17)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.