Homepage
About Snyk

com.typesafe.akka:akka-actor_2.12@2.5.14 vulnerabilities

Go back to all versions of this package
Report a new vulnerability Found a mistake?

Direct Vulnerabilities

Known vulnerabilities in the com.typesafe.akka:akka-actor_2.12 package. This does not include vulnerabilities belonging to this package’s dependencies.

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.
Fix for free
Vulnerability Vulnerable Version
  • M
Generation of Predictable Numbers or Identifiers

com.typesafe.akka:akka-actor_2.12 is a toolkit for building highly concurrent, distributed, and resilient message-driven applications for Java and Scala.

Affected versions of this package are vulnerable to Generation of Predictable Numbers or Identifiers in the async-dns resolver component, which is used by Discovery in DNS mode and transitively by Cluster Bootstrap. It uses predictable DNS transaction IDs when resolving DNS records, making DNS resolution subject to poisoning by an attacker. If the application performing discovery does not validate (e.g., via TLS) the authenticity of the discovered service, this may result in exfiltration of application data (e.g., persistence events may be published to an unintended Kafka broker). If such validation is performed, then the poisoning constitutes a denial of access to the intended service.

The complexity of a successful attack using this vulnerability is high because the attacker must gather or guess details about the services accessible via the affected DNS server.

How to fix Generation of Predictable Numbers or Identifiers?

Upgrade com.typesafe.akka:akka-actor_2.12 to version 2.8.1 or higher.

[2.5.14,2.8.1)
  • C
Insecure Random Number Generation

com.typesafe.akka:akka-actor_2.12 is a toolkit for building highly concurrent, distributed, and resilient message-driven applications for Java and Scala.

Affected versions of this package are vulnerable to Insecure Random Number Generation. When a custom random number generator is configured, if the AES128CounterSecureRNG and AES256CounterSecureRNG are enabled, a malicious user could easily guess the random number used during encryption and possibly eavesdrop onto ongoing communications. This is due a bug in the AES128CounterSecureRNG and AES256CounterSecureRNG implementations, causing the generated numbers to repeat themselves after a few bytes.

How to fix Insecure Random Number Generation?

Upgrade com.typesafe.akka:akka-actor_2.12 to version 2.5.16 or higher.

[2.5.0,2.5.16)
Go back to all versions of this package