Overview 7 matches · 4 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
4
57.1%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
3
42.9%
blocked by ARMR today
4
57.1%
partly blocked
0
0.0%
not blocked
3
42.9%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
7
100.0%
split by
peak 3 / quarter
Q3 151
Protected by Waratek1
High1
blocked by ARMR today1
No public exploit1
Q4 150
Q1 160
Q2 160
Q3 160
Q4 160
Q1 170
Q2 170
Q3 170
Q4 170
Q1 180
Q2 180
Q3 180
Q4 180
Q1 190
Q2 190
Q3 193
Protected by Waratek2
No exploit published1
Critical2
High1
blocked by ARMR today2
not blocked1
No public exploit3
Q4 190
Q1 200
Q2 200
Q3 201
No exploit published1
Medium1
not blocked1
No public exploit1
Q4 201
Protected by Waratek1
Critical1
blocked by ARMR today1
No public exploit1
Q1 210
Q2 211
No exploit published1
High1
not blocked1
No public exploit1
Q4 15Q2 16Q4 16Q2 17Q4 17Q2 18Q4 18Q2 19Q4 19Q2 20Q4 20Q2 21
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2021-30638 | High | 2021-04-27 | No exploit published | No public exploit | Information Exposure vulnerability in context asset handling of Apache Tapestry allows an attacker to download files inside WEB-INF if using a specially-constructed URL. This was caused by an incomplete fix for CVE-2020-13953. This issue affects Apache Tapestry Apache Tapestry 5.4.0 version to Apache Tapestry 5.6.3; Apache Tapestry 5.7.0 version and Apache Tapestry 5.7.1. |
| CVE-2020-17531 | Critical | 2020-12-08 | Protected by Waratek | No public exploit | A Java Serialization vulnerability was found in Apache Tapestry 4. Apache Tapestry 4 will attempt to deserialize the "sp" parameter even before invoking the page's validate method, leading to deserialization without authentication. Apache Tapestry 4 reached end of life in 2008 and no update to address this issue will be released. Apache Tapestry 5 versions are not vulnerable to this issue. Users of Apache Tapestry 4 should upgrade to the latest Apache Tapestry 5 version. |
| CVE-2020-13953 | Medium | 2020-09-30 | No exploit published | No public exploit | In Apache Tapestry from 5.4.0 to 5.5.0, crafting specific URLs, an attacker can download files inside the WEB-INF folder of the WAR being run. |
| CVE-2019-10071 | Critical | 2019-09-16 | No exploit published | No public exploit | 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. |
| CVE-2019-0207 | High | 2019-09-16 | Protected by Waratek | No public exploit | Tapestry processes assets `/assets/ctx` using classes chain `StaticFilesFilter -> AssetDispatcher -> ContextResource`, which doesn't filter the character `\`, so attacker can perform a path traversal attack to read any files on Windows platform. |
| CVE-2019-0195 | Critical | 2019-09-16 | Protected by Waratek | No public exploit | Manipulating classpath asset file URLs, an attacker could guess the path to a known file in the classpath and have it downloaded. If the attacker found the file with the value of the tapestry.hmac-passphrase configuration symbol, most probably the webapp's AppModule class, the value of this symbol could be used to craft a Java deserialization attack, thus running malicious injected Java code. The vector would be the t:formdata parameter from the Form component. |
| CVE-2014-1972 | High | 2015-08-22 | Protected by Waratek | No public exploit | 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. |