Overview 105 matches · 39 protected · 54 exploited · 12 CISA KEV · 28 EPSS ≥ 0.5
Protected by Waratek
41
39.0%
Rule in development
3
2.9%
Mitigation candidate
61
58.1%
No exploit published
0
0.0%
blocked by ARMR today
39
37.1%
partly blocked
2
1.9%
not blocked
64
61.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
54
51.4%
Working exploit published
37
35.2%
Proof of concept only
14
13.3%
Forecast only
0
0.0%
No public exploit
0
0.0%
split by
peak 14 / quarter
Q2 248
Protected by Waratek4
Mitigation candidate4
Critical4
High4
blocked by ARMR today4
not blocked4
Exploited6
Working exploit published1
Proof of concept only1
Q3 2411
Protected by Waratek5
Mitigation candidate6
Critical3
High6
Medium2
blocked by ARMR today3
partly blocked2
not blocked6
Exploited4
Working exploit published6
Proof of concept only1
Q4 249
Protected by Waratek4
Mitigation candidate5
Critical6
High2
Low1
blocked by ARMR today4
not blocked5
Exploited3
Working exploit published4
Proof of concept only2
Q1 255
Protected by Waratek2
Mitigation candidate3
Critical2
High1
Medium2
blocked by ARMR today2
not blocked3
Exploited4
Working exploit published1
Q2 2513
Protected by Waratek4
Rule in development1
Mitigation candidate8
Critical5
High3
Medium5
blocked by ARMR today4
not blocked9
Exploited8
Working exploit published4
Proof of concept only1
Q3 2510
Protected by Waratek4
Mitigation candidate6
Critical5
High1
Medium4
blocked by ARMR today4
not blocked6
Exploited7
Working exploit published3
Q4 2512
Protected by Waratek5
Rule in development2
Mitigation candidate5
Critical5
High3
Medium4
blocked by ARMR today5
not blocked7
Exploited7
Working exploit published4
Proof of concept only1
Q1 268
Protected by Waratek2
Mitigation candidate6
Critical3
High3
Medium1
Low1
blocked by ARMR today2
not blocked6
Exploited2
Working exploit published2
Proof of concept only4
Q2 2614
Protected by Waratek8
Mitigation candidate6
Critical4
High6
Medium4
blocked by ARMR today8
not blocked6
Exploited7
Working exploit published5
Proof of concept only2
Q3 2613
Protected by Waratek2
Mitigation candidate11
Critical7
High4
Medium2
blocked by ARMR today2
not blocked11
Exploited5
Working exploit published7
Proof of concept only1
Q4 262
Protected by Waratek1
Mitigation candidate1
Critical1
High1
blocked by ARMR today1
not blocked1
Exploited1
Proof of concept only1
Q2 24Q3 24Q4 24Q1 25Q2 25Q3 25Q4 25Q1 26Q2 26Q3 26Q4 26
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2024-35219 | High | 2024-05-27 | Protected by Waratek | Exploited | OpenAPI Generator allows generation of API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec. Prior to version 7.6.0, attackers can exploit a path traversal vulnerability to read and delete files and folders from an arbitrary, writable directory as anyone can set the output folder when submitting the request via the `outputFolder` option. The issue was fixed in version 7.6.0 by removing the usage of the `outputFolder` option. No known workarounds are available. |
| CVE-2024-32114 | High | 2024-05-02 | Mitigation candidate | Exploited | In Apache ActiveMQ 6.x, the default configuration doesn't secure the API web context (where the Jolokia JMX REST API and the Message REST API are located). It means that anyone can use these layers without any required authentication. Potentially, anyone can interact with the broker (using Jolokia JMX REST API) and/or produce/consume messages or purge/delete destinations (using the Message REST API). To mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement: <bean id="securityConstraintMapping" class="org.eclipse.jetty.security.ConstraintMapping"> <property name="constraint" ref="securityConstraint" /> <property name="pathSpec" value="/" /> </bean> Or we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default. |
| CVE-2024-27348 | Critical | 2024-04-22 | Protected by Waratek | Exploited | RCE-Remote Command Execution vulnerability in Apache HugeGraph-Server.This issue affects Apache HugeGraph-Server: from 1.0.0 before 1.3.0 in Java8 & Java11 Users are recommended to upgrade to version 1.3.0 with Java11 & enable the Auth system, which fixes the issue. |
| CVE-2024-21006 | High | 2024-04-16 | Mitigation candidate | Proof of concept only | Vulnerability in the Oracle WebLogic Server product of Oracle Fusion Middleware (component: Core). Supported versions that are affected are 12.2.1.4.0 and 14.1.1.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via T3, IIOP to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle WebLogic Server accessible data. CVSS 3.1 Base Score 7.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). |
| CVE-2024-31982 | Critical | 2024-04-10 | Mitigation candidate | Exploited | XWiki Platform is a generic wiki platform. Starting in version 2.4-milestone-1 and prior to versions 4.10.20, 15.5.4, and 15.10-rc-1, XWiki's database search allows remote code execution through the search text. This allows remote code execution for any visitor of a public wiki or user of a closed wiki as the database search is by default accessible for all users. This impacts the confidentiality, integrity and availability of the whole XWiki installation. This vulnerability has been patched in XWiki 14.10.20, 15.5.4 and 15.10RC1. As a workaround, one may manually apply the patch to the page `Main.DatabaseSearch`. Alternatively, unless database search is explicitly used by users, this page can be deleted as this is not the default search interface of XWiki. |