Remote code execution in Apache Tapestry
Published 16 Jun 2021 · Updated 2 Dec 2024
Is your project on an affected org.apache.tapestry:tapestry-core?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=5.4.0 <5.6.3
- Fixed in
- 5.6.3
mvn versions:use-dep-version -Dincludes=org.apache.tapestry:tapestry-core -DdepVersion=5.6.3 -DforceVersion=true- Affected
- >=5.7.0 <5.7.1
- Fixed in
- 5.7.1
mvn versions:use-dep-version -Dincludes=org.apache.tapestry:tapestry-core -DdepVersion=5.7.1 -DforceVersion=trueDetails
A critical unauthenticated remote code execution vulnerability was found all recent versions of Apache Tapestry. The affected versions include 5.4.5, 5.5.0, 5.6.2 and 5.7.0. The vulnerability I have found is a bypass of the fix for CVE-2019-0195. Recap: Before the fix of CVE-2019-0195 it was possible to download arbitrary class files from the classpath by providing a crafted asset file URL. An attacker was able to download the file AppModule.class by requesting the URL http://localhost:8080/assets/something/services/AppModule.class which contains a HMAC secret key. The fix for that bug was a blacklist filter that checks if the URL ends with .class, .properties or .xml. Bypass: Unfortunately, the blacklist solution can simply be bypassed by appending a / at the end of the URL: http://localhost:8080/assets/something/services/AppModule.class/ The slash is stripped after the blacklist check and the file AppModule.class is loaded into the response. This class usually contains the HMAC secret key which is used to sign serialized Java objects. With the knowledge of that key an attacker can sign a Java gadget chain that leads to RCE (e.g. CommonsBeanUtils1 from ysoserial). Solution for this vulnerability: * For Apache Tapestry 5.4.0 to 5.6.2, upgrade to 5.6.3 or later. * For Apache Tapestry 5.7.0, upgrade to 5.7.1 or later.
Is GHSA-mj8x-cpr8-x39h in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.apache.tapestry:tapestry-core, and gives you the command that fixes it.
More advisories for org.apache.tapestry:tapestry-core
- CriticalCVE-2022-46366Apache Tapestry allows deserialization of untrusted data · 2 Dec 2022
- HighCVE-2022-31781Apache Tapestry 5.8.1 vulnerable to ReDoS via Content Types causing catastrophic backtracking · 14 Jul 2022
- CriticalCVE-2019-0195Deserialization of Untrusted Data in Apache Tapestry · 24 May 2022
- HighCVE-2014-1972Apache Tapestry Unsafe Object Storage · 13 May 2022
- HighCVE-2021-30638Information Exposure in Apache Tapestry · 18 Mar 2022
- MediumCVE-2020-13953Improper file downloads in Apache Tapestry · 10 Feb 2022
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2021-27850
- Linkissues.apache.org/jira/browse/TAP5-2663
- Linklists.apache.org/thread.html/r237ff7f286bda31682c254550c1ebf92b0ec61329b32fbeb2d1c8751%40%3Cusers.tapestry.apache.org%3E
- Linksecurity.netapp.com/advisory/ntap-20210528-0002
- Linkwww.openwall.com/lists/oss-security/2021/04/15/1
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.