GitHub Advisoryadvisory · Maven
GHSA-mr95-9rr4-668f Cryptographically Weak Pseudo-Random Number Generator (PRNG) in akka-actor
CRITICAL
Official page ↗
- Aliases
- CVE-2018-16115
- Ecosystem
- Maven
- Packages
- com.typesafe.akka:akka-actor_2.11, com.typesafe.akka:akka-actor_2.12
- Severity
- Critical
- CVSS vector
- CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- Weaknesses
- CWE-338
- Reviewed
- 2020-06-16
Affected packages
• Maven com.typesafe.akka:akka-actor_2.11: >= 2.5.0, < 2.5.16 → fixed in 2.5.16
• Maven com.typesafe.akka:akka-actor_2.12: >= 2.5.0, < 2.5.16 → fixed in 2.5.16
Description
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.
Related
Alias · CVE (1)
- CVE-2018-16115 Lightbend Akka 2.5.x before 2.5.16 allows message disclosure and modification because of an RNG error. vulnerability
Weakness · CWE (1)
- CWE-338 Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) weakness