CVE-2023-45142 is an uncontrolled resource-consumption vulnerability in OpenTelemetry Go Contrib's otelhttp HTTP server instrumentation. The handler wrapper records attacker-controlled HTTP method and User-Agent values as metric attributes through httpconv.ServerRequest. Because these attributes may have unbounded cardinality, repeated requests using unique or excessively long values cause the metrics pipeline to retain an ever-growing set of time series or attribute values, resulting in increasing memory consumption. Version 0.44.0 restricts the collected http.request.method attribute to recognized methods and removes other high-cardinality attributes.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
26 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A denial-of-service vulnerability in the OpenTelemetry otelhttp component.
A denial-of-service vulnerability in OpenTelemetry otelhttp.
A denial-of-service vulnerability in the OpenTelemetry otelhttp component, addressed by the OADP 1.3.1 security update.
Denial-of-service vulnerability in the OpenTelemetry otelhttp component.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.