Overview 117 matches · 18 protected · 6 exploited · 2 CISA KEV · 10 public PoC · 5 EPSS ≥ 0.5
Protected by Waratek
18
15.4%
Rule in development
1
0.9%
Mitigation candidate
6
5.1%
No exploit published
92
78.6%
blocked by ARMR today
18
15.4%
partly blocked
0
0.0%
not blocked
99
84.6%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 28 / quarter
Q4 238
Protected by Waratek1
Mitigation candidate2
No exploit published5
High4
Medium4
blocked by ARMR today1
not blocked7
Working exploit published2
No public exploit6
Q1 241
No exploit published1
High1
not blocked1
No public exploit1
Q2 245
Protected by Waratek3
No exploit published2
Critical4
High1
blocked by ARMR today3
not blocked2
Exploited2
Forecast only1
No public exploit2
Q3 241
No exploit published1
Critical1
not blocked1
No public exploit1
Q4 241
Mitigation candidate1
Low1
not blocked1
Working exploit published1
Q1 253
Protected by Waratek1
No exploit published2
Critical1
High1
Medium1
blocked by ARMR today1
not blocked2
Proof of concept only1
No public exploit2
Q2 2515
Protected by Waratek1
Mitigation candidate1
No exploit published13
Critical2
High1
Medium10
Low2
blocked by ARMR today1
not blocked14
Exploited1
Proof of concept only1
No public exploit13
Q3 2517
Protected by Waratek3
No exploit published14
Critical1
High5
Medium11
blocked by ARMR today3
not blocked14
Exploited1
Proof of concept only1
No public exploit15
Q4 2511
Protected by Waratek1
Rule in development1
Mitigation candidate1
No exploit published8
Critical3
High4
Medium4
blocked by ARMR today1
not blocked10
Exploited1
Working exploit published1
No public exploit9
Q1 262
No exploit published2
Critical1
High1
not blocked2
No public exploit2
Q2 2623
Protected by Waratek5
No exploit published18
Critical4
High9
Medium9
Low1
blocked by ARMR today5
not blocked18
Proof of concept only3
No public exploit20
Q3 2628
Protected by Waratek3
Mitigation candidate1
No exploit published24
Critical5
High9
Medium14
blocked by ARMR today3
not blocked25
Exploited1
Proof of concept only2
No public exploit25
Q4 262
No exploit published2
Medium2
not blocked2
Proof of concept only1
No public exploit1
Q4 23Q2 24Q4 24Q2 25Q4 25Q2 26Q4 26
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2025-0851 | Critical | 2025-01-29 | Protected by Waratek | No public exploit | A path traversal issue in ZipUtils.unzip and TarUtils.untar in Deep Java Library (DJL) on all platforms allows a bad actor to write files to arbitrary locations. |
| CVE-2024-56512 | Low | 2024-12-28 | Mitigation candidate | Working exploit published | Apache NiFi 1.10.0 through 2.0.0 are missing fine-grained authorization checking for Parameter Contexts, referenced Controller Services, and referenced Parameter Providers, when creating new Process Groups. Creating a new Process Group can include binding to a Parameter Context, but in cases where the Process Group did not reference any Parameter values, the framework did not check user authorization for the bound Parameter Context. Missing authorization for a bound Parameter Context enabled clients to download non-sensitive Parameter values after creating the Process Group. Creating a new Process Group can also include referencing existing Controller Services or Parameter Providers. The framework did not check user authorization for referenced Controller Services or Parameter Providers, enabling clients to create Process Groups and use these components that were otherwise unauthorized. This vulnerability is limited in scope to authenticated users authorized to create Process Groups. The scope is further limited to deployments with component-based authorization policies. Upgrading to Apache NiFi 2.1.0 is the recommended mitigation, which includes authorization checking for Parameter and Controller Service references on Process Group creation. |
| CVE-2024-43202 | Critical | 2024-08-20 | No exploit published | No public exploit | Exposure of Remote Code Execution in Apache Dolphinscheduler. This issue affects Apache DolphinScheduler: before 3.2.2. We recommend users to upgrade Apache DolphinScheduler to version 3.2.2, which fixes the issue. |
| CVE-2024-37902 | Critical | 2024-06-17 | Protected by Waratek | No public exploit | DeepJavaLibrary(DJL) is an Engine-Agnostic Deep Learning Framework in Java. DJL versions 0.1.0 through 0.27.0 do not prevent absolute path archived artifacts from inserting archived files directly into the system, overwriting system files. This is fixed in DJL 0.28.0 and patched in DJL Large Model Inference containers version 0.27.0. Users are advised to upgrade. |
| 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-27349 | Critical | 2024-04-22 | No exploit published | No public exploit | Authentication Bypass by Spoofing vulnerability in Apache HugeGraph-Server.This issue affects Apache HugeGraph-Server: from 1.0.0 before 1.3.0. Users are recommended to upgrade to version 1.3.0, which fixes the issue. |
| 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-31997 | Critical | 2024-04-10 | No exploit published | Forecast only | XWiki Platform is a generic wiki platform. Prior to versions 4.10.19, 15.5.4, and 15.10-rc-1, parameters of UI extensions are always interpreted as Velocity code and executed with programming rights. Any user with edit right on any document like the user's own profile can create UI extensions. This allows remote code execution and thereby impacts the confidentiality, integrity and availability of the whole XWiki installation. This vulnerability has been patched in XWiki 14.10.19, 15.5.4 and 15.9-RC1. No known workarounds are available. |
| CVE-2023-5685 | High | 2024-03-22 | No exploit published | No public exploit | A flaw was found in XNIO. The XNIO NotifierState that can cause a Stack Overflow Exception when the chain of notifier states becomes problematically large can lead to uncontrolled resource management and a possible denial of service (DoS). |
| CVE-2023-6911 | Medium | 2023-12-18 | No exploit published | No public exploit | Multiple WSO2 products have been identified as vulnerable due to improper output encoding, a Stored Cross Site Scripting (XSS) attack can be carried out by an attacker injecting a malicious payload into the Registry feature of the Management Console. |
| CVE-2023-6837 | High | 2023-12-15 | No exploit published | No public exploit | Multiple WSO2 products have been identified as vulnerable to perform user impersonatoin using JIT provisioning. In order for this vulnerability to have any impact on your deployment, following conditions must be met: * An IDP configured for federated authentication and JIT provisioning enabled with the "Prompt for username, password and consent" option. * A service provider that uses the above IDP for federated authentication and has the "Assert identity using mapped local subject identifier" flag enabled. Attacker should have: * A fresh valid user account in the federated IDP that has not been used earlier. * Knowledge of the username of a valid user in the local IDP. When all preconditions are met, a malicious actor could use JIT provisioning flow to perform user impersonation. |
| CVE-2023-6836 | High | 2023-12-15 | Protected by Waratek | No public exploit | Multiple WSO2 products have been identified as vulnerable due to an XML External Entity (XXE) attack abuses a widely available but rarely used feature of XML parsers to access sensitive information. |
| CVE-2023-6835 | Medium | 2023-12-15 | No exploit published | No public exploit | Multiple WSO2 products have been identified as vulnerable due to lack of server-side input validation in the Forum feature, API rating could be manipulated. |
| CVE-2023-50720 | Medium | 2023-12-15 | Mitigation candidate | Working exploit published | XWiki Platform is a generic wiki platform. Prior to versions 14.10.15, 15.5.2, and 15.7-rc-1, the Solr-based search in XWiki discloses the email addresses of users even when obfuscation of email addresses is enabled. To demonstrate the vulnerability, search for `objcontent:email*` using XWiki's regular search interface. This has been fixed in XWiki 14.10.15, 15.5.2 and 15.7RC1 by not indexing email address properties when obfuscation is enabled. There are no known workarounds for this vulnerability. |
| CVE-2023-50719 | High | 2023-12-15 | Mitigation candidate | Working exploit published | XWiki Platform is a generic wiki platform. Starting in 7.2-milestone-2 and prior to versions 14.10.15, 15.5.2, and 15.7-rc-1, the Solr-based search in XWiki discloses the password hashes of all users to anyone with view right on the respective user profiles. By default, all user profiles are public. This vulnerability also affects any configurations used by extensions that contain passwords like API keys that are viewable for the attacker. Normally, such passwords aren't accessible but this vulnerability would disclose them as plain text. This has been patched in XWiki 14.10.15, 15.5.2 and 15.7RC1. There are no known workarounds for this vulnerability. |
| CVE-2023-47324 | Medium | 2023-12-13 | No exploit published | No public exploit | Silverpeas Core 6.3.1 is vulnerable to Cross Site Scripting (XSS) via the message/notification feature. |
| CVE-2023-47323 | High | 2023-12-13 | No exploit published | No public exploit | The notification/messaging feature of Silverpeas Core 6.3.1 does not enforce access control on the ID parameter. This allows an attacker to read all messages sent between other users; including those sent only to administrators. |