GHSA-p9p4-97g9-wcrh

    Dashboard / Vulnerabilities / GHSA-p9p4-97g9-wcrh

    GHSA-p9p4-97g9-wcrh

    Published: 3 Jun 2022Last Modified: 3 Nov 2025

    Summary: Dev error stack trace leaking into prod in Play Framework

    Details: ### 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 changed to use the prod-mode behavior, and `DevHttpErrorHandler` has been introduced for the dev-mode behavior. ### Workarounds When constructing a `CORSFilter` or `CORSActionBuilder`, ensure that a properly-configured error handler is passed. Generally this should be done by using the `HttpErrorHandler` instance provided through dependency injection or through Play's `BuiltInComponents`. Ensure that your application is not using the `DefaultHttpErrorHandler` static object in any code that may be run in production. ### References https://www.playframework.com/documentation/2.8.x/ScalaErrorHandling#Supplying-a-custom-error-handler https://www.playframework.com/documentation/2.8.x/JavaErrorHandling#Supplying-a-custom-error-handler ### For more information If you have any questions or comments about this advisory: * Open an issue in [playframework/playframework](https://github.com/playframework/playframework/) * Email us at [[email protected]](mailto:[email protected])

    References: https://github.com/playframework/playframework/security/advisories/GHSA-p9p4-97g9-wcrh, https://nvd.nist.gov/vuln/detail/CVE-2022-31023, https://github.com/playframework/playframework/pull/11305, https://github.com/playframework/playframework, https://github.com/playframework/playframework/releases/tag/2.8.16

    Affected packages

    Package

    Name: com.typesafe.play:play_2.12

    Purl: pkg:maven/com.typesafe.play/play_2.12

    Affected ranges

    Type: ECOSYSTEM

    Events:

    Introduced- 0
    Fixed -2.8.16

    Affected versions

    2.6.0
    2.6.0-M1
    2.6.0-M2
    2.6.0-M3
    2.6.0-M4
    2.6.0-M5
    2.6.0-RC1
    2.6.0-RC2
    2.6.1
    2.6.10
    2.6.11
    2.6.12
    2.6.13
    2.6.14
    2.6.15
    2.6.16
    2.6.17
    2.6.18
    2.6.19
    2.6.2
    2.6.20
    2.6.21
    2.6.22
    2.6.23
    2.6.24
    2.6.25
    2.6.3
    2.6.5
    2.6.6
    2.6.7
    2.6.9

    Common Vulnerability Scoring System

    Attack Vector
    Network
    Adjacent
    Local
    Physical
    Privileges Required
    None
    Low
    High
    User Interaction
    None
    Required
    Scope
    Unchanged
    Changed
    Confidentiality
    None
    Low
    High
    Integrity
    None
    Low
    High
    Availability
    None
    Low
    High
    GHSA-p9p4-97g9-wcrh | CVE-DB