Apache Tapestry before 5.3.6 relies on client-side object storage without checking whether a client has modified an object, which allows remote attackers to cause a denial of service (resource consumption) or execute arbitrary code via crafted serialized data.

References

• https://nvd.nist.gov/vuln/detail/CVE-2014-1972
• https://issues.apache.org/jira/browse/TAP5-2008
• https://lists.apache.org/thread.html/84e99dedad2ecb4676de93c3ab73a8a10882951ab6984f514707f3d9@%3Cusers.tapestry.apache.org%3E
• https://lists.apache.org/thread.html/bac8d6f9e1b4059b319d9cba6f33219a99b81623476ec896138f851c@%3Cusers.tapestry.apache.org%3E
• https://lists.apache.org/thread.html/r7d9c54beb1dc97dcccc58d9b5d31f0f7166f9a25ad1beba5f8091e0c@%3Ccommits.tapestry.apache.org%3E
• https://lists.apache.org/thread.html/r87523dd07886223aa086edc25fe9b8ddb9c1090f7db25b068dc30843@%3Ccommits.tapestry.apache.org%3E
• https://tapestry.apache.org/release-notes-536.html
• http://jvn.jp/en/jp/JVN17611367/index.html
• http://jvndb.jvn.jp/jvndb/JVNDB-2015-000118
• http://seclists.org/fulldisclosure/2019/Aug/20
• http://www.openwall.com/lists/oss-security/2019/08/23/5
• apache/tapestry-5@5ad5257