Envoy up to 1.27.5/1.28.3/1.29.4/11.30.1 Mirror Response resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Envoy up to 1.27.5/1.28.3/1.29.4/11.30.1. This issue affects some unknown processing of the component Mirror Response Handler. Performing a manipulation results in resource consumption. This vulnerability is reported as CVE-2024-34364. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in Envoy up to 1.27.5/1.28.3/1.29.4/11.30.1. It has been classified as problematic. This affects an unknown code of the component Mirror Response Handler. The manipulation with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on availability. The summary by CVE is:
Envoy is a cloud-native, open source edge and service proxy. Envoy exposed an out-of-memory (OOM) vector from the mirror response, since async HTTP client will buffer the response with an unbounded buffer.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-34364 since 05/02/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. It demands that the victim is doing some kind of user interaction. 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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
- 1.27.0
- 1.27.1
- 1.27.2
- 1.27.3
- 1.27.4
- 1.27.5
- 1.28.0
- 1.28.1
- 1.28.2
- 1.28.3
- 1.29.0
- 1.29.1
- 1.29.2
- 1.29.3
- 1.29.4
- 11.30.0
- 11.30.1
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.0VulDB Meta Temp Score: 6.0
VulDB Base Score: 5.7
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CNA Base Score: 5.7
CNA Vector (GitHub, Inc.): 🔍
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: 🔍
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
05/02/2024 🔍06/05/2024 🔍
06/05/2024 🔍
03/26/2025 🔍
Sources
Advisory: GHSA-xcj3-h7vf-fw26Status: Confirmed
CVE: CVE-2024-34364 (🔍)
GCVE (CVE): GCVE-0-2024-34364
GCVE (VulDB): GCVE-100-267117
Entry
Created: 06/05/2024 03:48Updated: 03/26/2025 06:14
Changes: 06/05/2024 03:48 (62), 06/06/2024 02:28 (1), 06/12/2024 17:38 (12), 03/26/2025 06:14 (3)
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.