Buoyant Edge up to 2.16.4/2.17.1/25.2.0 Linkerd Proxy Metrics resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in Buoyant Edge up to 2.16.4/2.17.1/25.2.0. This vulnerability affects unknown code of the component Linkerd Proxy Metrics Handler. Such manipulation leads to resource consumption. This vulnerability is uniquely identified as CVE-2025-43915. No exploit exists. You should upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in Buoyant Edge up to 2.16.4/2.17.1/25.2.0. Affected by this issue is some unknown functionality of the component Linkerd Proxy Metrics Handler. The manipulation with an unknown input leads to a resource consumption vulnerability. Using CWE to declare the problem leads to 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. Impacted is availability. CVE summarizes:
In Buoyant Edge releases before edge-25.2.1 and Enterprise for Linkerd releases 2.16.* before 2.16.5, 2.17.* before 2.17.2, and 2.18.* before 2.18.0, resource exhaustion can occur for Linkerd proxy metrics.
The advisory is available at buoyant.io. This vulnerability is handled as CVE-2025-43915 since 04/19/2025. The technical details are unknown and an exploit is not available.
Upgrading to version 2.16.5, 2.17.2, 2.18.0 or 25.2.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-13396). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Partially
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Edge 2.16.5/2.17.2/2.18.0/25.2.1
Timeline
04/19/2025 🔍05/05/2025 🔍
05/05/2025 🔍
05/19/2025 🔍
Sources
Advisory: buoyant.ioStatus: Confirmed
CVE: CVE-2025-43915 (🔍)
GCVE (CVE): GCVE-0-2025-43915
GCVE (VulDB): GCVE-100-307442
EUVD: 🔍
Entry
Created: 05/05/2025 18:47Updated: 05/19/2025 21:12
Changes: 05/05/2025 18:47 (55), 05/15/2025 21:25 (1), 05/19/2025 21:12 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.