CVE-2022-46366 Apache Tapestry prior to version 4 (EOL) allows RCE though deserialization of untrusted input

Critical 9.8 Published Updated

Attackers can achieve remote code execution by exploiting unsafe deserialization in the unsupported Apache Tapestry 3.x library.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2022-46366?

CVE-2022-46366 is a critical unsafe deserialization vulnerability in Apache Tapestry, published on 2 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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.

Weakness: CWE-502

Which versions are affected by CVE-2022-46366?

2 open source packages ship an affected version, including org.apache.tapestry:tapestry-core. It affects 1 product.

PackageAffectedFixed in
org.apache.tapestry:tapestry-core MavenFrom 3.05.0.1
org.apache.tapestry:tapestry-core MavenFrom 3.05.0.1

Products include Apache Tapestry.

How do I fix CVE-2022-46366?

Upgrade org.apache.tapestry:tapestry-core to 5.0.1 or later.

Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.

Is CVE-2022-46366 being exploited?

There is no known exploitation of CVE-2022-46366 in the wild and no public exploit code.

Sources

Also known as GHSA-vc39-x7w6-6vj7.

Is CVE-2022-46366 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free