Cryptographically Weak Pseudo-Random Number Generator (PRNG) in akka-actor
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| com.typesafe.akka:akka-actor_2.11 Maven |
|
|
| com.typesafe.akka:akka-actor_2.12 Maven |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| com.typesafe.akka:akka-actor_2.11 Maven |
|
|
| com.typesafe.akka:akka-actor_2.12 Maven |
|
|
Lightbend Akka 2.5.x before 2.5.16 allows message disclosure and modification because of an RNG error. A random number generator is used in Akka Remoting for TLS (both classic and Artery Remoting). Akka allows configuration of custom random number generators. For historical reasons, Akka included the AES128CounterSecureRNG and AES256CounterSecureRNG random number generators. The implementations had a bug that caused the generated numbers to be repeated after only a few bytes. The custom RNG implementations were not configured by default but examples in the documentation showed (and therefore implicitly recommended) using the custom ones. This can be used by an attacker to compromise the communication if these random number generators are enabled in configuration. It would be possible to eavesdrop, replay, or modify the messages sent with Akka Remoting/Cluster.
From the CVE record · mitre
Akka 2.5.x before 2.5.16 includes buggy custom random number generators that repeat generated numbers after only a few bytes. If AES128CounterSecureRNG or AES256CounterSecureRNG is enabled in configuration, an attacker could eavesdrop on, replay, or modify messages sent through Akka Remoting or Cluster; these generators are not enabled by default.
Engineers running Maven com.typesafe.akka:akka-actor_2.11 or akka-actor_2.12 versions 2.5.0 through 2.5.15 should check their deployments.