In versions of dd-trace-java prior to 1.60.3, the RMI instrumentation registered a custom endpoint that deserialized incoming data without applying serialization filters. On JDK version 16 and earlier, an attacker with network access to a JMX or RMI port on an instrumented JVM could exploit this to potentially achieve remote code execution. All three of the following conditions must be true to exploit this vulnerability: 1. dd-trace-java is attached as a Java agent (`-javaagent`) on Java 16 or earlier 2. A JMX/RMI port has been explicitly configured via `-Dcom.sun.management.jmxremote.port` and is network-reachable 3. A gadget-chain-compatible library is present on the classpath ### Impact Arbitrary remote code execution with the privileges of the user running the instrumented JVM. ### Recommendation - For JDK >= 17: No action is required, but upgrading is strongly encouraged. - For JDK >= 8u121 < JDK 17: Upgrade to dd-trace-java version 1.60.3 or later. - For JDK < 8u121 and earlier where serialization filters are not available, apply the workaround described below. ### Workarounds Set the following environment variable to disable the RMI integration: `DD_INTEGRATION_RMI_ENABLED=false` ### Credits This vulnerability was responsibly disclosed by Mohamed Amine ait Ouchebou (mrecho) (Indiesecurity) via the Datadog bug bounty program.
In versions of dd-trace-java prior to 1.60.3, the RMI instrumentation registered a custom endpoint that deserialized incoming data without applying serialization filters. On JDK version 16 and earlier, an attacker with network access to a JMX or RMI port on an instrumented JVM could exploit this to potentially achieve remote code execution. All three of the following conditions must be true to exploit this vulnerability: 1. dd-trace-java is attached as a Java agent (`-javaagent`) on Java 16 or earlier 2. A JMX/RMI port has been explicitly configured via `-Dcom.sun.management.jmxremote.port` and is network-reachable 3. A gadget-chain-compatible library is present on the classpath ### Impact Arbitrary remote code execution with the privileges of the user running the instrumented JVM. ### Recommendation - For JDK >= 17: No action is required, but upgrading is strongly encouraged. - For JDK >= 8u121 < JDK 17: Upgrade to dd-trace-java version 1.60.3 or later. - For JDK < 8u121 and earlier where serialization filters are not available, apply the workaround described below. ### Workarounds Set the following environment variable to disable the RMI integration: `DD_INTEGRATION_RMI_ENABLED=false` ### Credits This vulnerability was responsibly disclosed by Mohamed Amine ait Ouchebou (mrecho) (Indiesecurity) via the Datadog bug bounty program.
Update com.datadoghq:dd-java-agent to 1.60.3 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scandd-trace-java: Unsafe deserialization in RMI instrumentation may lead to remote code execution affects com.datadoghq:dd-java-agent (maven). Severity is critical. In versions of dd-trace-java prior to 1.60.3, the RMI instrumentation registered a custom endpoint that deserialized incoming data without applying serialization filters. On JDK version 16 and earlier, an attacker with network access to a JMX or RMI port on an instrumented JVM could exploit this to potentially achieve remote code execution. All three of the following conditions must be true to exploit this vulnerability: 1. dd-trace-java is attached as a Java agent (`-javaagent`) on Java 16 or earlier 2. A JMX/RMI port has been explicitly configured via `-Dcom.sun.management.jmxremote.port` and is network-reachable 3. A gadget-chain-compatible library is present on the classpath ### Impact Arbitrary remote code execution with the privileges of the user running the instrumented JVM. ### Recommendation - For JDK >= 17: No action is required, but upgrading is strongly encouraged. - For JDK >= 8u121 < JDK 17: Upgrade to dd-trace-java version 1.60.3 or later. - For JDK < 8u121 and earlier where serialization filters are not available, apply the workaround described below. ### Workarounds Set the following environment variable to disable the RMI integration: `DD_INTEGRATION_RMI_ENABLED=false` ### Credits This vulnerability was responsibly disclosed by Mohamed Amine ait Ouchebou (mrecho) (Indiesecurity) via the Datadog bug bounty program.
AI coding agents often install or upgrade packages automatically in maven. A critical vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| com.datadoghq:dd-java-agentmaven | >=0.40.0,<1.60.3 | 1.60.3 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate com.datadoghq:dd-java-agent to 1.60.3 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scandd-trace-java: Unsafe deserialization in RMI instrumentation may lead to remote code execution affects com.datadoghq:dd-java-agent (maven). Severity is critical. In versions of dd-trace-java prior to 1.60.3, the RMI instrumentation registered a custom endpoint that deserialized incoming data without applying serialization filters. On JDK version 16 and earlier, an attacker with network access to a JMX or RMI port on an instrumented JVM could exploit this to potentially achieve remote code execution. All three of the following conditions must be true to exploit this vulnerability: 1. dd-trace-java is attached as a Java agent (`-javaagent`) on Java 16 or earlier 2. A JMX/RMI port has been explicitly configured via `-Dcom.sun.management.jmxremote.port` and is network-reachable 3. A gadget-chain-compatible library is present on the classpath ### Impact Arbitrary remote code execution with the privileges of the user running the instrumented JVM. ### Recommendation - For JDK >= 17: No action is required, but upgrading is strongly encouraged. - For JDK >= 8u121 < JDK 17: Upgrade to dd-trace-java version 1.60.3 or later. - For JDK < 8u121 and earlier where serialization filters are not available, apply the workaround described below. ### Workarounds Set the following environment variable to disable the RMI integration: `DD_INTEGRATION_RMI_ENABLED=false` ### Credits This vulnerability was responsibly disclosed by Mohamed Amine ait Ouchebou (mrecho) (Indiesecurity) via the Datadog bug bounty program.
AI coding agents often install or upgrade packages automatically in maven. A critical vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| com.datadoghq:dd-java-agentmaven | >=0.40.0,<1.60.3 | 1.60.3 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard