WaratekVRT Sign in
Reset
More filters (2)
Columns
Published to 2022-03-31✕Product security✕
Overview 105 matches · 18 protected · 10 exploited · 5 CISA KEV · 20 public PoC · 11 EPSS ≥ 0.5
split by peak 28 / year
No exploit published: 74Mitigation candidate: 13Protected by Waratek: 18 Low: 4Medium: 44High: 44Critical: 13 not blocked: 87blocked by ARMR today: 18 No public exploit: 85Proof of concept only: 4Working exploit published: 6Exploited: 10
20051 Mitigation candidate1 High1 not blocked1 Working exploit published1 20060 20070 20080 20090 20102 Protected by Waratek1 No exploit published1 Medium2 blocked by ARMR today1 not blocked1 Working exploit published1 No public exploit1 20111 Protected by Waratek1 Medium1 blocked by ARMR today1 Proof of concept only1 20123 Mitigation candidate1 No exploit published2 Medium3 not blocked3 Working exploit published1 No public exploit2 20133 Protected by Waratek2 No exploit published1 Medium2 Low1 blocked by ARMR today2 not blocked1 No public exploit3 20143 No exploit published3 Medium3 not blocked3 No public exploit3 20152 No exploit published2 Medium2 not blocked2 No public exploit2 20162 No exploit published2 High2 not blocked2 No public exploit2 201712 Protected by Waratek1 Mitigation candidate1 No exploit published10 Critical1 High8 Medium2 Low1 blocked by ARMR today1 not blocked11 Exploited1 No public exploit11 201813 Protected by Waratek1 No exploit published12 Critical3 High6 Medium4 blocked by ARMR today1 not blocked12 No public exploit13 201928 Protected by Waratek4 Mitigation candidate6 No exploit published18 Critical4 High11 Medium12 Low1 blocked by ARMR today4 not blocked24 Exploited3 Working exploit published3 Proof of concept only1 No public exploit21 202014 Mitigation candidate1 No exploit published13 Critical1 High7 Medium5 Low1 not blocked14 Exploited1 No public exploit13 202117 Protected by Waratek8 Mitigation candidate2 No exploit published7 Critical3 High7 Medium7 blocked by ARMR today8 not blocked9 Exploited4 Proof of concept only2 No public exploit11 20224 Mitigation candidate1 No exploit published3 Critical1 High2 Medium1 not blocked4 Exploited1 No public exploit3
200620082010201220142016201820202022
105 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed. ‹ prev page 2 of 2 next ›
CVE Severity Published▾ Status Exploitation Description
CVE-2011-2731 Medium 2012-12-05 No exploit published No public exploit Race condition in the RunAsManager mechanism in VMware SpringSource Spring Security before 2.0.7 and 3.0.x before 3.0.6 stores the Authentication object in the shared security context, which allows attackers to gain privileges via a crafted thread.
CVE-2011-2894 Medium 2011-10-04 Protected by Waratek Proof of concept only Spring Framework 3.0.0 through 3.0.5, Spring Security 3.0.0 through 3.0.5 and 2.0.0 through 2.0.6, and possibly other versions deserialize objects from untrusted sources, which allows remote attackers to bypass intended security restrictions and execute untrusted code by (1) serializing a java.lang.Proxy instance and using InvocationHandler, or (2) accessing internal AOP interfaces, as demonstrated using deserialization of a DefaultListableBeanFactory instance to execute arbitrary commands via the java.lang.Runtime class.
CVE-2010-3863 Medium 2010-11-05 Protected by Waratek Working exploit published Apache Shiro before 1.1.0, and JSecurity 0.9.x, does not canonicalize URI paths before comparing them to entries in the shiro.ini file, which allows remote attackers to bypass intended access restrictions via a crafted request, as demonstrated by the /./account/index.jsp URI.
CVE-2010-3700 Medium 2010-10-29 No exploit published No public exploit VMware SpringSource Spring Security 2.x before 2.0.6 and 3.x before 3.0.4, and Acegi Security 1.0.0 through 1.0.7, as used in IBM WebSphere Application Server (WAS) 6.1 and 7.0, allows remote attackers to bypass security constraints via a path parameter.
CVE-2004-1029 High 2005-03-01 Mitigation candidate Working exploit published The Sun Java Plugin capability in Java 2 Runtime Environment (JRE) 1.4.2_01, 1.4.2_04, and possibly earlier versions, does not properly restrict access between Javascript and Java applets during data transfer, which allows remote attackers to load unsafe classes and execute arbitrary code by using the reflection API to access private Java packages.
‹ prev page 2 of 2 next ›