First published: Thu Jun 02 2022(Updated: )
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.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Lightbend Play Framework | >=2.8.3<=2.8.15 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-31018 is a denial of service vulnerability in versions 2.8.3 through 2.8.15 of Play's forms library in the Play Framework for Java and Scala.
The severity of CVE-2022-31018 is high, with a CVSS score of 7.5.
CVE-2022-31018 affects versions 2.8.3 through 2.8.15 of Play's forms library in both the Scala and Java APIs.
To fix CVE-2022-31018, update Play Framework to version 2.8.16 or higher.
Yes, you can find additional information about CVE-2022-31018 in the following references: [link1], [link2], [link3].