CVE-2022-31023: Dev error stack trace leaking into prod in Play Framework

CVE-2022-31023 · Severity: low · CVSS 3.1 · Published 2022-06-03

Dev error stack trace leaking into prod in Play Framework

Technologies: com.typesafe.play:play_2.12 (Maven). Vendors: Maven.

Quick answers

Is CVE-2022-31023 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-31023 being exploited in the wild.
How severe is CVE-2022-31023?
Low severity, with a CVSS score of 3.1, published 3 June 2022.
Which products and versions are affected?
com.typesafe.play:play_2.12 (Maven) ECOSYSTEM:introduced=0,fixed=2.8.16; com.typesafe.play:play_2.13 (Maven) ECOSYSTEM:introduced=0,fixed=2.8.16.
Is there a fix for CVE-2022-31023?
Yes. com.typesafe.play:play_2.12 (Maven): upgrade to 2.8.16 or later; com.typesafe.play:play_2.13 (Maven): upgrade to 2.8.16 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-31023?
Check whether you run com.typesafe.play:play_2.12 (Maven) or com.typesafe.play:play_2.13 (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

  • com.typesafe.play:play_2.12 (Maven): upgrade to 2.8.16 or later
    # set com.typesafe.play:play_2.12 to 2.8.16 in your pom.xml or build.gradle
  • com.typesafe.play:play_2.13 (Maven): upgrade to 2.8.16 or later
    # set com.typesafe.play:play_2.13 to 2.8.16 in your pom.xml or build.gradle

Affected products

  • com.typesafe.play:play_2.12 (Maven) ECOSYSTEM:introduced=0,fixed=2.8.16
  • com.typesafe.play:play_2.13 (Maven) ECOSYSTEM:introduced=0,fixed=2.8.16

Identifiers

  • CVE-2022-31023
  • GHSA-p9p4-97g9-wcrh

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.