Approved changes feed: RSS · Atom

cpe:2.3:a:lightbend:play_framework:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorLightbend (eeba8d5c-f0b3-5068-b0af-843cc375ab14)
ProductPlay Framework (5ad058f8-c0c3-5e57-8cce-8b901055bcb7)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/playframework/playframework purl2cpe 2026-06-01 10:16:12.993368

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2022-31023 vulnerable 2026-06-08 05:43:40.000326 Dev error stack trace leaking into prod in Play Framework
MEDIUM (5.9)
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.
Published: 2022-06-02T18:05:11.000Z
Updated: 2025-04-23T18:19:50.789Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2022-31018 vulnerable 2026-06-08 05:43:39.993785 Denial of service binding form from JSON in Play Framework
HIGH (7.5)
Play Framework is a web framework for Java and Scala. A denial of service vulnerability has been discovered in verions 2.8.3 through 2.8.15 of Play's forms library, in both the Scala and Java APIs. This can occur when using either the `Form#bindFromRequest` method on a JSON request body or the `Form#bind` method directly on a JSON value. If the JSON data being bound to the form contains a deeply-nested JSON object or array, the form binding implementation may consume all available heap space and cause an `OutOfMemoryError`. If executing on the default dispatcher and `akka.jvm-exit-on-fatal-error` is enabled—as it is by default—then this can crash the application process. `Form.bindFromRequest` is vulnerable when using any body parser that produces a type of `AnyContent` or `JsValue` in Scala, or one that can produce a `JsonNode` in Java. This includes Play's default body parser. This vulnerability been patched in version 2.8.16. There is now a global limit on the depth of a JSON object that can be parsed, which can be configured by the user if necessary. As a workaround, applications that do not need to parse a request body of type `application/json` can switch from the default body parser to another body parser that supports only the specific type of body they expect.
Published: 2022-06-02T16:45:13.000Z
Updated: 2025-04-23T18:20:02.455Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2020-28923 vulnerable 2026-06-08 05:23:56.600981 Details available
An issue was discovered in Play Framework 2.8.0 through 2.8.4. Carefully crafted JSON payloads sent as a form field lead to Data Amplification. This affects users migrating from a Play version prior to 2.8.0 that used the Play Java API to serialize classes with protected or private fields to JSON.
Published: 2020-12-03T16:21:31.000Z
Updated: 2024-08-04T16:41:00.239Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2020-27196 vulnerable 2026-06-08 05:23:52.229206 Details available
An issue was discovered in PlayJava in Play Framework 2.6.0 through 2.8.2. The body parsing of HTTP requests eagerly parses a payload given a Content-Type header. A deep JSON structure sent to a valid POST endpoint (that may or may not expect JSON payloads) causes a StackOverflowError and Denial of Service.
Published: 2020-11-06T13:24:18.000Z
Updated: 2024-08-04T16:11:35.939Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2020-26883 vulnerable 2026-06-08 05:23:51.631491 Details available
In Play Framework 2.6.0 through 2.8.2, stack consumption can occur because of unbounded recursion during parsing of crafted JSON documents.
Published: 2020-11-06T13:21:29.000Z
Updated: 2024-08-04T16:03:22.569Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2020-26882 vulnerable 2026-06-08 05:23:51.630933 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2020-12480 vulnerable 2026-06-08 05:17:58.248671 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2019-17598 vulnerable 2026-06-08 05:13:10.799772 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2018-13864 vulnerable 2026-06-08 05:10:52.034290 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.