Dev error stack trace leaking into prod in Play Framework

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2022-31023: 1.35% estimated exploitation activity in the next 30 days; percentile 71.52 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Play Framework, when run in dev mode, shows verbose errors for easy debugging, including an exception stack trace. Play does this by configuring its DefaultHttpErrorHandler to do so based on the application mode. In its Scala API Play also provides a static object DefaultHttpErrorHandler that is configured to always show verbose errors. This is used as a default value in some Play APIs, so it is possible to inadvertently use this version in production. It is also possible to improperly configure the DefaultHttpErrorHandler object instance as the injected error handler. Both of these situations could result in verbose errors displaying to users in a production application, which could expose sensitive information from the application. In particular the constructor for CORSFilter and apply method for CORSActionBuilder use the static object DefaultHttpErrorHandler as a default value. Patches This is patched in Play Framework 2.8.16. The DefaultHttpErrorHandler object has been…

Published by the source

3 Jun 2022, 22:19 UTC

Last modified by the source

3 Nov 2025, 21:05 UTC

Source last checked

26 Oct 2026, 16:40 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-p9p4-97g9-wcrh

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-31023

Advisory: Dev error stack trace leaking into prod in Play Framework
IDs: CVE-2022-31023, GHSA-p9p4-97g9-wcrh
Record: https://patchnext.com/advisories/cve-2022-31023 (revision 1, source checked 26 Oct 2026, 16:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.typesafe.play:play_2.12 2.8.16; com.typesafe.play:play_2.13 2.8.16. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.typesafe.play:play_2.12: affected < 2.8.16; fixed in 2.8.16
- Maven com.typesafe.play:play_2.13: affected < 2.8.16; fixed in 2.8.16

## Suggested inspection (read-only)
- Maven com.typesafe.play:play_2.12: check the installed version with your package manager.
- Maven com.typesafe.play:play_2.13: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.typesafe.play:play_2.12, com.typesafe.play:play_2.13.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-p9p4-97g9-wcrh (GitHub-reviewed advisory GHSA-p9p4-97g9-wcrh lists affected ranges: Maven com.typesafe.play:play_2.12 >=0 =0 <2.8.16)

Commands are suggestions: review each one before running it.