CVE-2024-28867 is a medium-severity (CVSS 5.9) CWE-74 vulnerability in github.com/swift-server/swift-prometheus. A fix is available for github.com/swift-server/swift-prometheus — see the affected versions and patch details below.
Swift Prometheus un-sanitized metric name or labels can be used to take over exported metrics
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-28867.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/swift-server/swift-prometheusReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects SwiftURL packages — download data is not available via public APIs for these ecosystems.
Description
Impact
In code which applies un-sanitized string values into metric names or labels, like this:
let lang = try? request.query-get(String.self, at: "lang")
Counter (
label: "language",
dimensions: [("lang", lang ?? "unknown" )]
)
an attacker could make use of this and send a ?lang query parameter containing newlines, } or similar characters which can lead to the attacker taking over the exported format -- including creating unbounded numbers of stored metrics, inflating server memory usage, or causing "bogus" metrics.
Patches
The default strategy to sanitize labels was moved deeper into the library, preventing illegal characters from appearing in name, label keys and values.
Metric names and label names are now validated against the following requirement: [a-zA-Z_:][a-zA-Z0-9_:]* (for metric names) and [a-zA-Z_][a-zA-Z0-9_]* (for metric label names). Label values are not validated as they are allowed to contain any unicode characters. Developers must validate labels themselves and not allow malicious input.
The approach taken here mirrors the approach taken in the Go reference implementation.
Discussion
It is strongly discouraged to use un-sanitized user input as names or labels in general, because they can lead to un-bounded growth of metrics, even as this vulnerability is patched and result in a Denial-of-Service attack opportunity -- regardless how well the library is sanitizing the inputs. We strongly recommend only using a sanitized set of values for your metrics names and labels. E.g., a "lang" label, should only use an expected set of values that can be used, and ignore other ones -- otherwise a determined attacker could create one metric per different label key, leading to unbounded memory use growth as metrics with distinct values must be kept in memory.
Validating label values:
The library will NOT automatically validate and replace strings offered as label values. Developers must validate label values themselves, and it is strongly recommended to only accept a well known set of values.
It is possible to configure the PrometheusSanitizer to apply whatever validation you deem necessary:
let mySanitizer = PrometheusSanitizer { metricName, labels in
// ... your logic here ...
(metricName, labels)
}
let registry = PrometheusCollectorRegistry(sanitizer: mySanitizer)
let factory = PrometheusMetricsFactory(factory: registry)
// swift-metrics
MetricsSystem.bootstrap(factory)
Workarounds
Developers must validate user input before using it as metric names, label names or values. This follows common practice of not trusting any user input without sanitization.
Credits
We would like to thank Jonas Dörr for bringing out attention to the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦SwiftURL | github.com/swift-server/swift-prometheus | ≥ 2.0.0-alpha.1&&< 2.0.0-alpha.2 | 2.0.0-alpha.2 |
Affected Products
swift prometheusappleDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/swift-server/swift-prometheus, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/swift-server/swift-prometheus to 2.0.0-alpha.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-28867 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2024-28867 in your dependencies?
Find it across SwiftURL, including transitive dependencies.