dd-trace-java: Improper parsing of W3C baggage headers may lead to DoS
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| DataDog | dd-trace-java | affected |
|
||||||
| com.datadoghq | dd-java-agent | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Datadog | Dd-java-agent |
|
||||||||
| Datadog | Dd-trace-java |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-74xj-wh4w-vqxc | dd-trace-java: Improper parsing of W3C baggage headers may lead to DoS |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.793% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Datadog
Datadog dd-java-agent Datadog dd-trace-java |
|
| Vendors & Products |
Datadog
Datadog dd-java-agent Datadog dd-trace-java |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | dd-trace-java: Improper parsing of W3C baggage headers may lead to DoS | |
| Weaknesses | CWE-770 | |
| References |
| |
| Metrics |
cvssV3_1
|