Overview 206 matches · 11 exploited · 2 CISA KEV · 14 public PoC · 6 EPSS ≥ 0.5
Protected by Waratek
206
100.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
blocked by ARMR today
206
100.0%
partly blocked
0
0.0%
not blocked
0
0.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 40 / quarter
Q4 2215
Protected by Waratek15
Critical2
High11
Medium2
blocked by ARMR today15
Proof of concept only1
No public exploit14
Q1 239
Protected by Waratek9
Critical2
High4
Medium3
blocked by ARMR today9
Proof of concept only3
No public exploit6
Q2 238
Protected by Waratek8
Critical2
High2
Medium4
blocked by ARMR today8
Exploited2
Proof of concept only1
Forecast only1
No public exploit4
Q3 2310
Protected by Waratek10
Critical2
High5
Medium2
Low1
blocked by ARMR today10
Exploited1
Proof of concept only5
No public exploit4
Q4 2310
Protected by Waratek10
Critical3
High6
Medium1
blocked by ARMR today10
Proof of concept only2
No public exploit8
Q1 2412
Protected by Waratek12
Critical2
High5
Medium5
blocked by ARMR today12
Exploited1
Working exploit published1
Proof of concept only2
Forecast only1
No public exploit7
Q2 247
Protected by Waratek7
Critical3
High3
Medium1
blocked by ARMR today7
Exploited2
Proof of concept only3
No public exploit2
Q3 246
Protected by Waratek6
Critical2
High4
blocked by ARMR today6
Exploited1
Proof of concept only1
No public exploit4
Q4 246
Protected by Waratek6
Critical2
High2
Medium2
blocked by ARMR today6
Exploited1
Working exploit published1
Proof of concept only1
No public exploit3
Q1 257
Protected by Waratek7
Critical1
High2
Medium4
blocked by ARMR today7
Proof of concept only2
No public exploit5
Q2 253
Protected by Waratek3
High1
Medium2
blocked by ARMR today3
Proof of concept only1
No public exploit2
Q3 257
Protected by Waratek7
Critical2
High1
Medium3
Low1
blocked by ARMR today7
Exploited2
Working exploit published1
No public exploit4
Q4 258
Protected by Waratek8
Critical1
Medium6
Low1
blocked by ARMR today8
Proof of concept only6
No public exploit2
Q1 2612
Protected by Waratek12
High8
Medium3
Low1
blocked by ARMR today12
Proof of concept only3
No public exploit9
Q2 2624
Protected by Waratek24
Critical6
High9
Medium8
Low1
blocked by ARMR today24
Proof of concept only6
No public exploit18
Q3 2640
Protected by Waratek40
Critical4
High16
Medium19
Low1
blocked by ARMR today40
Working exploit published1
Proof of concept only4
No public exploit35
Q4 2622
Protected by Waratek22
Critical3
High7
Medium11
Low1
blocked by ARMR today22
Exploited1
Proof of concept only7
No public exploit14
Q4 22Q2 23Q4 23Q2 24Q4 24Q2 25Q4 25Q2 26Q4 26
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-42123 | High | 2022-11-15 | Protected by Waratek | No public exploit | A Zip slip vulnerability in the Elasticsearch Connector in Liferay Portal 7.3.3 through 7.4.3.18, and Liferay DXP 7.3 before update 6, and 7.4 before update 19 allows attackers to create or overwrite existing files on the filesystem via the installation of a malicious Elasticsearch Sidecar plugin. |
| CVE-2022-37866 | High | 2022-11-07 | Protected by Waratek | No public exploit | When Apache Ivy downloads artifacts from a repository it stores them in the local file system based on a user-supplied "pattern" that may include placeholders for artifacts coordinates like the organisation, module or version. If said coordinates contain "../" sequences - which are valid characters for Ivy coordinates in general - it is possible the artifacts are stored outside of Ivy's local cache or repository or can overwrite different artifacts inside of the local cache. In order to exploit this vulnerability an attacker needs collaboration by the remote repository as Ivy will issue http requests containing ".." sequences and a "normal" repository will not interpret them as part of the artifact coordinates. Users of Apache Ivy 2.0.0 to 2.5.1 should upgrade to Ivy 2.5.1. |
| CVE-2022-37865 | Critical | 2022-11-07 | Protected by Waratek | No public exploit | With Apache Ivy 2.4.0 an optional packaging attribute has been introduced that allows artifacts to be unpacked on the fly if they used pack200 or zip packaging. For artifacts using the "zip", "jar" or "war" packaging Ivy prior to 2.5.1 doesn't verify the target path when extracting the archive. An archive containing absolute paths or paths that try to traverse "upwards" using ".." sequences can then write files to any location on the local fie system that the user executing Ivy has write access to. Ivy users of version 2.4.0 to 2.5.0 should upgrade to Ivy 2.5.1. |
| CVE-2022-32287 | High | 2022-11-03 | Protected by Waratek | No public exploit | A relative path traversal vulnerability in a FileUtil class used by the PEAR management component of Apache UIMA allows an attacker to create files outside the designated target directory using carefully crafted ZIP entry names. This issue affects Apache UIMA Apache UIMA version 3.3.0 and prior versions. Note that PEAR files should never be installed into an UIMA installation from untrusted sources because PEAR archives are executable plugins that will be able to perform any actions with the same privileges as the host Java Virtual Machine. |
| CVE-2022-34662 | Medium | 2022-11-01 | Protected by Waratek | No public exploit | When users add resources to the resource center with a relation path will cause path traversal issues and only for logged-in users. You could upgrade to version 3.0.0 or higher |
| CVE-2022-26884 | Medium | 2022-10-28 | Protected by Waratek | No public exploit | Users can read any files by log server, Apache DolphinScheduler users should upgrade to version 2.0.6 or higher. |