CVE-2022-31023: Dev error stack trace leaking into prod in Play Framework
First published: Thu Jun 02 2022(Updated: )
Play Framework is a web framework for Java and Scala. Verions prior to 2.8.16 are vulnerable to generation of error messages containing sensitive information. 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. 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. A workaround is available. 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 the application is not using the `DefaultHttpErrorHandler` static object in any code that may be run in production.
Credit: security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Lightbend Play Framework | <2.8.16 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is CVE-2022-31023?
CVE-2022-31023 is a vulnerability in Play Framework versions prior to 2.8.16 that allows the generation of error messages containing sensitive information. When running in dev mode, Play Framework shows verbose errors including an exception stack trace.
How does CVE-2022-31023 impact Play Framework?
CVE-2022-31023 impacts Play Framework by allowing error messages with sensitive information to be generated, potentially exposing sensitive data in the error output.
What is the severity of CVE-2022-31023?
CVE-2022-31023 has a severity rating of high with a CVSS score of 7.5.
How can I fix CVE-2022-31023?
To fix CVE-2022-31023, you should update Play Framework to version 2.8.16 or later, which includes the necessary security fixes.
Where can I find more information about CVE-2022-31023?
You can find more information about CVE-2022-31023 on the Play Framework GitHub repository, including the pull request, release notes, and security advisory.
- collector/nvd-index
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/remedy
- agent/references
- agent/author
- agent/weakness
- agent/severity
- agent/last-modified-date
- agent/tags
- agent/title
- agent/description
- agent/event
- agent/first-publish-date
- vendor/lightbend
- canonical/lightbend play framework