WaratekVRT Sign in
Reset
More filters (2)
Columns
EPSS ≥ 0.5✕Product banking platform✕
Overview 2 matches · 1 protected · 0 exploited · 0 CISA KEV · 1 public PoC
2matches 1protected50.0% 0exploited0.0% 0CISA KEV0.0% 1public PoC50.0%
Protected by Waratek 1 50.0% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 1 50.0%
Critical 0 0.0% High 2 100.0% Medium 0 0.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 1 50.0% partly blocked 0 0.0% not blocked 1 50.0% not established 0 0.0% unrecorded 0 0.0%
Exploited 0 0.0% Working exploit published 1 50.0% Proof of concept only 0 0.0% Forecast only 1 50.0% No public exploit 0 0.0%
split by peak 1 / month
No exploit published: 1Protected by Waratek: 1 High: 2 not blocked: 1blocked by ARMR today: 1 Forecast only: 1Working exploit published: 1
Nov 20Dec 20Jan 21Feb 21Mar 21
2 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
CVE-2021-21341 High 2021-03-23 No exploit published Forecast only XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is vulnerability which may allow a remote attacker to allocate 100% CPU time on the target system depending on CPU type or parallel execution of such a payload resulting in a denial of service only by manipulating the processed input stream. No user is affected who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
CVE-2020-26217 High 2020-11-16 Protected by Waratek Working exploit published XStream before version 1.4.14 is vulnerable to Remote Code Execution.The vulnerability may allow a remote attacker to run arbitrary shell commands only by manipulating the processed input stream. Only users who rely on blocklists are affected. Anyone using XStream's Security Framework allowlist is not affected. The linked advisory provides code workarounds for users who cannot upgrade. The issue is fixed in version 1.4.14.