CVE-2022-31781 json
Regular Expression Denial of Service (ReDoS) in ContentType.java. (GHSL-2022-022)
published 2022-07-13 4 y ago modified 2026-06-17 4 mo ago also GHSA-227g-7cvv-6ff3 , EUVD-2022-6199
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
Apache Tapestry up to version 5.8.1 is vulnerable to Regular Expression Denial of Service (ReDoS) in the way it handles Content Types. Specially crafted Content Types may cause catastrophic backtracking, taking exponential time to complete. Specifically, this is about the regular expression used on the parameter of the org.apache.tapestry5.http.ContentType class. Apache Tapestry 5.8.2 has a fix for this vulnerability. Notice the vulnerability cannot be triggered by web requests in Tapestry code alone. It would only happen if there's some non-Tapestry codepath passing some outside input to the ContentType class constructor.
Patch / fix
- maven org.apache.tapestry:tapestry-core 5.8.2
- apache tapestry 5.8.2
Exploit prediction
1.97% chance of exploitation in the next 30 days, higher than 80% 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 |
| 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 | org.apache.tapestry:tapestry-core | <5.8.2 |
5.8.2 |
Affected products
- Apache Software Foundation Apache Tapestry
Classification
References
-
github.com
/apache/tapestry-5/commit/3c8d6103832eec3bc06029dd2532f06df717431f
web
-
openwall.com
/lists/oss-security/2022/07/12/3
web, mailing-list, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-31781
advisory
Sources
- CVE List CVE-2022-31781
- GitHub Advisory GHSA-227g-7cvv-6ff3
- NVD CVE-2022-31781
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.