CVE-2020-27196 json
Out-of-bounds Write in Play Framework
published 2020-11-06 6 y ago modified 2026-06-17 4 mo ago also GHSA-h48w-c35p-6m8x , EUVD-2022-1032
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 72%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven com.typesafe.play:play 2.7.6, 2.8.3
- maven com.typesafe.play:play-java 2.7.6, 2.8.3
- github.com/playframework/playframework#10321 pull request
Exploit prediction
1.40% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | com.typesafe.play:play | >=2.6.0, <2.7.6 >=2.8.0, <2.8.3 |
2.7.6 2.8.3 |
| maven | com.typesafe.play:play-java | >=2.6.0, <2.7.6 >=2.8.0, <2.8.3 |
2.7.6 2.8.3 |
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
github.com
/playframework/playframework/pull/10321
web
-
playframework.com
/security/vulnerability
vendor-advisory
-
playframework.com
/security/vulnerability/CVE-2020-27196-DosViaJsonStackOverflow
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-27196
advisory
Sources
- CVE List CVE-2020-27196
- GitHub Advisory GHSA-h48w-c35p-6m8x
- NVD CVE-2020-27196
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.