Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsUpgrade com.typesafe.akka:akka-discovery_2.12
to version 2.8.1 or higher.
com.typesafe.akka:akka-discovery_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.