Apache Tapestry Unsafe Object Storage
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2014-1972US | high7.8 | — | ||
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 servi… | ||||
02
references
External citations — patches, advisories, analysis.
- http://jvn.jp/en/jp/JVN17611367/index.htmlWEB
- http://jvndb.jvn.jp/jvndb/JVNDB-2015-000118WEB
- http://seclists.org/fulldisclosure/2019/Aug/20WEB
- http://www.openwall.com/lists/oss-security/2019/08/23/5WEB
- https://github.com/apache/tapestry-5WEB
- https://github.com/apache/tapestry-5/commit/5ad5257fdfacbad2c7c480fdf2afa15d9a37e6b0WEB
- https://issues.apache.org/jira/browse/TAP5-2008WEB
- https://lists.apache.org/thread.html/84e99dedad2ecb4676de93c3ab73a8a10882951ab6984f514707f3d9@%3Cusers.tapestry.apache.org%3EWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan