io.opentelemetry.javaagent:opentelemetry-javaagent@2.1.0
latest version
2.31.0
latest non vulnerable version
first published
5 years ago
latest version published
3 days ago
licenses detected
- [0.12.0,)
package registry
Direct Vulnerabilities
Known vulnerabilities in the io.opentelemetry.javaagent:opentelemetry-javaagent package. This does not include vulnerabilities belonging to this package’s dependencies.
Fix vulnerabilities automatically
Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.
Fix for free| Vulnerability | Vulnerable Version |
|---|---|
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the RMI context propagation process. An attacker can cause excessive memory allocation by sending an oversized context propagation payload to a network-reachable RMI endpoint on an instrumented JVM, potentially resulting in resource exhaustion and service disruption. This is only exploitable if RMI instrumentation is enabled and the RMI endpoint is accessible over the network. How to fix Allocation of Resources Without Limits or Throttling? Upgrade | [,2.27.0) |
Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File in the process of logging SQL CONNECT statements, where passwords enclosed in double quotes are not properly sanitized. An attacker can obtain sensitive database credentials by accessing exported trace span attributes that include these clear-text passwords. How to fix Insertion of Sensitive Information into Log File? Upgrade | [,2.28.0) |
Affected versions of this package are vulnerable to Deserialization of Untrusted Data in the RMI integration. An attacker can execute arbitrary code with the privileges of the user running the instrumented JVM by sending specially crafted serialized data to a network-exposed JMX or RMI port. Note: This is only exploitable if the agent is attached as a Java agent on Java 16 or earlier, a JMX/RMI port is explicitly configured and network-reachable, and a gadget-chain-compatible library is present on the classpath. How to fix Deserialization of Untrusted Data? Upgrade | [,2.26.1) |