The code which checks HMAC in form submissions used String.equals() for comparisons, which results in a timing side channel for the comparison of the HMAC signatures. This could lead to remote code execution if an attacker is able to determine the correct signature for their payload. The comparison should be done with a constant time algorithm instead.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HApache Tapestry
APPApache5.4.0 – 5.4.3
Related vulnerabilities
Apache Tapestry 3.x allows deserialization of untrusted data, leading to remote code execution. This issue is ...
A critical unauthenticated remote code execution vulnerability was found all recent versions of Apache Tapestr...
A Java Serialization vulnerability was found in Apache Tapestry 4. Apache Tapestry 4 will attempt to deseriali...
Manipulating classpath asset file URLs, an attacker could guess the path to a known file in the classpath and ...
Apache Tapestry up to version 5.8.1 is vulnerable to Regular Expression Denial of Service (ReDoS) in the way i...