CVE-2019-11808: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) in Ratpack

Quick answers

Is CVE-2019-11808 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2019-11808 being exploited in the wild.

How severe is CVE-2019-11808?

Low severity, with a CVSS score of 3, published 14 May 2019.

Which products and versions are affected?

io.ratpack:ratpack-groovy (Maven) ECOSYSTEM:introduced=0,fixed=1.6.1; io.ratpack:ratpack-java (Maven) ECOSYSTEM:introduced=0,fixed=1.6.1; io.ratpack:ratpack-session (Maven) ECOSYSTEM:introduced=0,fixed=1.6.1.

Is there a fix for CVE-2019-11808?

Yes. io.ratpack:ratpack-groovy (Maven): upgrade to 1.6.1 or later; io.ratpack:ratpack-java (Maven): upgrade to 1.6.1 or later; io.ratpack:ratpack-session (Maven): upgrade to 1.6.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2019-11808?

Check whether you run io.ratpack:ratpack-groovy (Maven), io.ratpack:ratpack-java (Maven) or io.ratpack:ratpack-session (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

• io.ratpack:ratpack-groovy (Maven): upgrade to 1.6.1 or later

  # set io.ratpack:ratpack-groovy to 1.6.1 in your pom.xml or build.gradle

• io.ratpack:ratpack-java (Maven): upgrade to 1.6.1 or later

  # set io.ratpack:ratpack-java to 1.6.1 in your pom.xml or build.gradle

• io.ratpack:ratpack-session (Maven): upgrade to 1.6.1 or later

  # set io.ratpack:ratpack-session to 1.6.1 in your pom.xml or build.gradle

Affected products

• io.ratpack:ratpack-groovy (Maven) ECOSYSTEM:introduced=0,fixed=1.6.1
• io.ratpack:ratpack-java (Maven) ECOSYSTEM:introduced=0,fixed=1.6.1
• io.ratpack:ratpack-session (Maven) ECOSYSTEM:introduced=0,fixed=1.6.1

Identifiers

• CVE-2019-11808
• GHSA-54mg-vgrp-mwx9