DataDog dd-trace-java
dd-trace-java: Improper parsing of W3C baggage headers may lead to DoS
dd-trace-java is a Datadog APM client for Java. Prior to 1.62.0, W3C baggage extraction does not enforce DD_TRACE_BAGGAGE_MAX_ITEMS, which defaults to 64, or DD_TRACE_BAGGAGE_MAX_BYTES, which defaults to 8192, although those limits apply during baggage injection. A remote unauthenticated attacker can send a baggage HTTP header containing many comma-separated key-value pairs or a single very large value. The extraction path allocates map entries while parsing the attacker-controlled header on every request, causing unbounded CPU and memory consumption in an HTTP service where the baggage propagation style is enabled, which is the default for most affected tracers. This can cause denial of service. This issue is fixed in version 1.62.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.62.0
Fixed in 1.62.0
- < 1.62.0
Fixed in 1.62.0
Mitigation
Upgrade dd-trace-java to 1.62.0 or later.
Upgrade dd-java-agent to 1.62.0 or later.
References
- Vendor advisory github.com/DataDog/dd-trace-java/security/advi…
- Patch github.com/DataDog/dd-trace-java/pull/11265
- Patch github.com/DataDog/dd-trace-java/commit/16c6a5…
1 more
- Release notes github.com/DataDog/dd-trace-java/releases/tag/…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.