Proxy memory exhaustion via unbounded hostname metrics
Published May 5, 2025 · Updated May 19, 2025
Resource exhaustion in Linkerd proxy metrics allows remote attackers to consume proxy memory through crafted HTTP requests. The proxy records every unique inbound authority or outbound hostname as a Prometheus metric label without bounding label cardinality. Exposure requires HTTP traffic with unconstrained hostnames; sustained requests can exhaust proxy memory, overwhelm metrics ingestion, or increase ingestion costs.
Summary
What happened
Resource exhaustion in Linkerd proxy metrics allows remote attackers to consume proxy memory through crafted HTTP requests. The proxy records every unique inbound authority or outbound hostname as a Prometheus metric label without bounding label cardinality. Exposure requires HTTP traffic with unconstrained hostnames; sustained requests can exhaust proxy memory, overwhelm metrics ingestion, or increase ingestion costs.
The record
- CVE
- CVE-2025-43915
- Published
- May 5, 2025
- Updated
- May 19, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, CWE-770, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 5, 2025CVE publishedPublication date reported by the CVE source.
- May 19, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo