Overview 4 matches · 2 protected · 1 exploited · 0 CISA KEV · 1 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
2
50.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
2
50.0%
blocked by ARMR today
2
50.0%
partly blocked
0
0.0%
not blocked
2
50.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
1
25.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
3
75.0%
split by
peak 2 / month
Jun 161
No exploit published1
Critical1
not blocked1
No public exploit1
Jul 160
Aug 160
Sep 160
Oct 160
Nov 160
Dec 160
Jan 170
Feb 170
Mar 170
Apr 170
May 172
Protected by Waratek2
Critical2
blocked by ARMR today2
Exploited1
No public exploit1
Jun 171
No exploit published1
Critical1
not blocked1
No public exploit1
Jun 16Aug 16Oct 16Dec 16Feb 17Apr 17Jun 17
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2016-3690 | Critical | 2017-06-08 | No exploit published | No public exploit | The PooledInvokerServlet in JBoss EAP 4.x and 5.x allows remote attackers to execute arbitrary code via a crafted serialized payload. |
| CVE-2017-7504 | Critical | 2017-05-19 | Protected by Waratek | Exploited | HTTPServerILServlet.java in JMS over HTTP Invocation Layer of the JbossMQ implementation, which is enabled by default in Red Hat Jboss Application Server <= Jboss 4.X does not restrict the classes for which it performs deserialization, which allows remote attackers to execute arbitrary code via crafted serialized data. |
| CVE-2017-7503 | Critical | 2017-05-18 | Protected by Waratek | No public exploit | It was found that the Red Hat JBoss EAP 7.0.5 implementation of javax.xml.transform.TransformerFactory is vulnerable to XXE. An attacker could use this flaw to launch DoS or SSRF attacks, or read files from the server where EAP is deployed. |
| CVE-2016-2141 | Critical | 2016-06-30 | No exploit published | No public exploit | It was found that JGroups did not require necessary headers for encrypt and auth protocols from new nodes joining the cluster. An attacker could use this flaw to bypass security restrictions, and use this vulnerability to send and receive messages within the cluster, leading to information disclosure, message spoofing, or further possible attacks. |