Exported metric corruption via unsanitized names
Published Mar 29, 2024 · Updated Mar 25, 2025
Output injection in Swift Prometheus 2.0.0-alpha.1 allows remote attackers to corrupt exported metrics via crafted names or labels. PrometheusCollectorRegistry accepts metric and label names without enforcing Prometheus grammar, so newlines and closing braces can escape the intended exposition field. Exploitation requires a consuming application to place attacker-controlled strings into those names; successful injection creates bogus metrics or unbounded stored metric series.
Summary
What happened
Output injection in Swift Prometheus 2.0.0-alpha.1 allows remote attackers to corrupt exported metrics via crafted names or labels. PrometheusCollectorRegistry accepts metric and label names without enforcing Prometheus grammar, so newlines and closing braces can escape the intended exposition field. Exploitation requires a consuming application to place attacker-controlled strings into those names; successful injection creates bogus metrics or unbounded stored metric series.
The record
- CVE
- CVE-2024-28867
- Published
- Mar 29, 2024
- Updated
- Mar 25, 2025
- Vendor
- Swift Server Workgroup
- Product
- Swift Prometheus
- Classifications
- CWE-74, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 29, 2024CVE publishedPublication date reported by the CVE source.
- Mar 25, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion== 2.0.0-alpha.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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