WaratekVRT Sign in
Reset
More filters (2)
Columns
Published from 2024-05-01✕Has a public PoC✕
Overview 101 matches · 38 protected · 52 exploited · 11 CISA KEV · 27 EPSS ≥ 0.5
split by peak 14 / quarter
Mitigation candidate: 58Rule in development: 3Protected by Waratek: 40 Low: 2Medium: 24High: 32Critical: 43 not blocked: 61partly blocked: 2blocked by ARMR today: 38 Proof of concept only: 12Working exploit published: 37Exploited: 52
Q2 245 Protected by Waratek3 Mitigation candidate2 Critical2 High3 blocked by ARMR today3 not blocked2 Exploited4 Working exploit published1 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 261 Protected by Waratek1 Critical1 blocked by ARMR today1 Exploited1
Q2 24Q3 24Q4 24Q1 25Q2 25Q3 25Q4 25Q1 26Q2 26Q3 26Q4 26
101 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-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.
‹ prev page 2 of 2 next ›