dbcve.org
TapestryApplication · Apache

CVE-2022-46366

CRITICAL · 9.8 CVSS v3.1 Published 2022-12-02
Fix available
A fix is available. Upgrade to 4.0.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Apache Tapestry 3.x allows deserialization of untrusted data, leading to remote code execution. This issue is similar to but distinct from CVE-2020-17531, which applies the the (also unsupported) 4.x version line. NOTE: This vulnerability only affects Apache Tapestry version line 3.x, which is no longer supported by the maintainer. Users are recommended to upgrade to a supported version line of Apache Tapestry.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Tapestry 3.x contains a deserialization vulnerability that allows remote code execution through unsafe deserialization of untrusted data. This is similar to CVE-2020-17531 but affects the 3.x version line specifically.

MitigationSince Apache Tapestry 3.x is no longer supported and receives no security patches, upgrade to a supported version line (5.x or 6.x). This requires a full version migration with testing to ensure compatibility.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TapestryApplication
Affected:>= 3.0.0, < 4.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Tapestry JAR files in the application
    Search for tapestry*.jar files in the application WEB-INF/lib directory, lib folder, or classpath. Check the file names for version indicators (e.g., tapestry-3.0.x.jar).
    Affected if Tapestry JAR files are found with version 3.x (3.0.0 through 3.9.x)
  2. Check MANIFEST.MF for Tapestry version
    Open the META-INF/MANIFEST.MF file inside any tapestry*.jar archive and look for the Implementation-Version or Bundle-Version attribute.
    Affected if The manifest shows a version in the range 3.0.0 to <4.0.0
  3. Verify application uses Tapestry deserialization features
    Search application code and configuration for usage of Hessian, Burlap, or Java serialization endpoints provided by Tapestry. Look in web.xml for servlet mappings to Tapestry serialization handlers.
    Affected if The application exposes endpoints that accept serialized Java objects through Tapestry's serialization framework
  4. Check if application accepts untrusted serialized data
    Review servlet configurations and filter mappings in web.xml and application documentation to determine if external clients can send serialized data to Tapestry endpoints.
    Affected if Tapestry serialization endpoints are accessible to untrusted clients without validation

The environment is affected if Apache Tapestry 3.x (version 3.0.0 through 3.9.x) is deployed AND the application exposes serialization endpoints that accept untrusted input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.0.0 or later
Fixed in 4.0.0
Interim mitigation

Since Apache Tapestry 3.x is no longer supported and receives no security patches, upgrade to a supported version line (5.x or 6.x). This requires a full version migration with testing to ensure compatibility.

Recommended fix High confidence

Apache Tapestry 5.x or later (currently supported version line)

  1. 1. Identify all applications and systems running Apache Tapestry 3.x (< 4.0.0)
  2. 2. Plan migration to a currently supported Apache Tapestry version line (5.x or later)
  3. 3. Review Tapestry migration guides for breaking changes between 3.x and target version
  4. 4. Update application dependencies to the new Tapestry version
  5. 5. Test application functionality thoroughly, as significant API changes exist between 3.x and 5.x
  6. 6. Redeploy the updated application
Caveat Significant; Tapestry 5.x has substantial API and architectural changes from 3.x, requiring code modifications

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tapestry Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA8.0 h
80.0 hours of engineering $13,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $22,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-46366 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-46366 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data