Overview 204 matches · 0 protected · 70 exploited · 5 CISA KEV · 182 public PoC · 49 EPSS ≥ 0.5
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
204
100.0%
No exploit published
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
198
97.1%
not established
6
2.9%
unrecorded
0
0.0%
split by
peak 40 / year
20194
Mitigation candidate4
Critical2
High1
Medium1
not blocked4
Exploited1
Working exploit published2
Proof of concept only1
202034
Mitigation candidate34
Critical11
High8
Medium15
not blocked34
Exploited10
Working exploit published14
Proof of concept only9
No public exploit1
202124
Mitigation candidate24
Critical4
High9
Medium11
not blocked24
Exploited9
Working exploit published8
Proof of concept only7
202221
Mitigation candidate21
Critical10
High8
Medium3
not blocked21
Exploited3
Working exploit published7
Proof of concept only10
No public exploit1
202340
Mitigation candidate40
Critical17
High13
Medium10
not blocked38
not established2
Exploited11
Working exploit published25
Proof of concept only3
No public exploit1
202429
Mitigation candidate29
Critical11
High12
Medium5
Low1
not blocked29
Exploited12
Working exploit published12
Proof of concept only5
202525
Mitigation candidate25
Critical8
High3
Medium14
not blocked23
not established2
Exploited17
Working exploit published8
202627
Mitigation candidate27
Critical10
High10
Medium6
Low1
not blocked25
not established2
Exploited7
Working exploit published11
Proof of concept only6
No public exploit3
20192020202120222023202420252026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2012-1592 | High | 2019-12-05 | Mitigation candidate | Working exploit published | A local code execution issue exists in Apache Struts2 when processing malformed XSLT files, which could let a malicious user upload and execute arbitrary files. |
| CVE-2019-12409 | Critical | 2019-11-18 | Mitigation candidate | Proof of concept only | The 8.1.1 and 8.2.0 releases of Apache Solr contain an insecure setting for the ENABLE_REMOTE_JMX_OPTS configuration option in the default solr.in.sh configuration file shipping with Solr. If you use the default solr.in.sh file from the affected releases, then JMX monitoring will be enabled and exposed on RMI_PORT (default=18983), without any authentication. If this port is opened for inbound traffic in your firewall, then anyone with network access to your Solr nodes will be able to access JMX, which may in turn allow them to upload malicious code for execution on the Solr server. |
| CVE-2011-3923 | Critical | 2019-11-01 | Mitigation candidate | Exploited | Apache Struts before 2.3.1.2 allows remote attackers to bypass security protections in the ParameterInterceptor class and execute arbitrary commands. |
| CVE-2019-10475 | Medium | 2019-10-23 | Mitigation candidate | Working exploit published | A reflected cross-site scripting vulnerability in Jenkins build-metrics Plugin allows attackers to inject arbitrary HTML and JavaScript into web pages provided by this plugin. |