Cloud Manager CVEs with no public exploit

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 0 0.0% Medium 1 50.0% Low 1 50.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 0 0.0% Proof of concept only 0 0.0% Forecast only 0 0.0% No public exploit 2 100.0%

split by StatusSeverityProtectionExploit maturity peak 1 / month

Apr 211 No exploit published1 Low1 not blocked1 No public exploit1 May 210 Jun 210 Jul 210 Aug 210 Sep 210 Oct 210 Nov 210 Dec 211 Protected by Waratek1 Medium1 blocked by ARMR today1 No public exploit1

Apr 21May 21Jun 21Jul 21Aug 21Sep 21Oct 21Nov 21Dec 21

CVE	Severity	Published▾	Status	Exploitation	Description
CVE-2021-42550	Medium	2021-12-16	Protected by Waratek	No public exploit	In logback version 1.2.7 and prior versions, an attacker with the required privileges to edit configurations files could craft a malicious configuration allowing to execute arbitrary code loaded from LDAP servers.
CVE-2021-28163	Low	2021-04-01	No exploit published	No public exploit	In Eclipse Jetty 9.4.32 to 9.4.38, 10.0.0.beta2 to 10.0.1, and 11.0.0.beta2 to 11.0.1, if a user uses a webapps directory that is a symlink, the contents of the webapps directory is deployed as a static webapp, inadvertently serving the webapps themselves and anything else that might be in that directory.

CVE

Severity

Published▾

Status

Exploitation

Description

CVE-2021-42550

Medium

2021-12-16

Protected by Waratek

No public exploit

In logback version 1.2.7 and prior versions, an attacker with the required privileges to edit configurations files could craft a malicious configuration allowing to execute arbitrary code loaded from LDAP servers.

CVE-2021-28163

Low

2021-04-01

No exploit published

No public exploit

In Eclipse Jetty 9.4.32 to 9.4.38, 10.0.0.beta2 to 10.0.1, and 11.0.0.beta2 to 11.0.1, if a user uses a webapps directory that is a symlink, the contents of the webapps directory is deployed as a static webapp, inadvertently serving the webapps themselves and anything else that might be in that directory.