CVE-2022-31781: Tapestry core Denial of Service Vulnerability

HIGH
Advisory Identifier: GHSA-227g-7cvv-6ff3
CVSS 7.5
CWE-400 CWE-1333
Published
Advisory Summary

CVE-2022-31781 is a HIGH (CVSS 7.5) denial of service vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting Tapestry core libraries in the Maven ecosystem. The issue involves apache tapestry 5.8.1 vulnerable to redos via content types causing catastrophic backtracking. Remediation is available by upgrading affected packages to version 5.8.2.

CVE-2022-31781 at a Glance

CVE Identifier CVE-2022-31781
GHSA Identifier GHSA-227g-7cvv-6ff3
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-400: Uncontrolled Resource Consumption
Affected Product Tapestry core
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2022-31781

To remediate this vulnerability, upgrade all affected Tapestry core dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.apache.tapestry:tapestry-core fixed: 5.8.2
<dependency>
    <groupId>org.apache.tapestry</groupId>
    <artifactId>tapestry-core</artifactId>
    <version>5.8.2</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=org.apache.tapestry

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2022-31781, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.apache.tapestry

Analyze the terminal output to locate any version of Tapestry core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.8.2), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.apache.tapestry command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-400: Uncontrolled Resource Consumption, where the product does not properly control the allocation and maintenance of a limited resource. In Tapestry core, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

CVE-2022-31781 Affected Tapestry core Versions

1 component(s)
Fixed Versions:
5.8.2
Product / Package Ecosystem Affected Versions Fixed Version
org.apache.tapestry:tapestry-core
Maven
< 5.8.2
5.8.2

References

Frequently Asked Questions

What is CVE-2022-31781?
CVE-2022-31781 is a security vulnerability in Tapestry core involving Apache Tapestry 5.8.1 vulnerable to ReDoS via Content Types causing catastrophic backtracking under CWE-400: Uncontrolled Resource Consumption.
Which Tapestry core versions are affected?
Affected versions include releases prior to 5.8.2 across affected packages: org.apache.tapestry:tapestry-core.
What version fixes CVE-2022-31781?
Upgrading to 5.8.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is tapestry-core affected?
Yes, org.apache.tapestry:tapestry-core is affected in releases prior to 5.8.2. Upgrade your dependency to 5.8.2 or later.
What is the CVSS score of CVE-2022-31781?
CVE-2022-31781 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2022-31781?
CVE-2022-31781 is classified under CWE-400: Uncontrolled Resource Consumption (The product does not properly control the allocation and maintenance of a limited resource.).
How can I check Maven dependencies for CVE-2022-31781?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.apache.tapestry'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-227g-7cvv-6ff3",
  "modified" : "2022-07-22T16:31:43Z",
  "published" : "2022-07-14T00:00:23Z",
  "aliases" : [ "CVE-2022-31781" ],
  "summary" : "Apache Tapestry 5.8.1 vulnerable to ReDoS via Content Types causing catastrophic backtracking",
  "details" : "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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.apache.tapestry:tapestry-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "5.8.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-31781"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/tapestry-5/commit/3c8d6103832eec3bc06029dd2532f06df717431f"
  }, {
    "type" : "WEB",
    "url" : "https://www.openwall.com/lists/oss-security/2022/07/12/3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-1333", "CWE-400" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2022-07-15T18:33:51Z",
    "nvd_published_at" : "2022-07-13T08:15:00Z"
  }
}