Overview 4 matches · 1 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
1
25.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
3
75.0%
blocked by ARMR today
1
25.0%
partly blocked
0
0.0%
not blocked
3
75.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
4
100.0%
split by
peak 1 / month
Jun 171
No exploit published1
High1
not blocked1
No public exploit1
Jul 170
Aug 170
Sep 170
Oct 171
No exploit published1
High1
not blocked1
No public exploit1
Nov 170
Dec 170
Jan 181
No exploit published1
High1
not blocked1
No public exploit1
Feb 180
Mar 180
Apr 180
May 181
Protected by Waratek1
High1
blocked by ARMR today1
No public exploit1
Jun 17Jul 17Aug 17Sep 17Oct 17Nov 17Dec 17Jan 18Feb 18Mar 18Apr 18May 18
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2018-1310 | High | 2018-05-23 | Protected by Waratek | No public exploit | Apache NiFi JMS Deserialization issue because of ActiveMQ client vulnerability. Malicious JMS content could cause denial of service. See ActiveMQ CVE-2015-5254 announcement for more information. The fix to upgrade the activemq-client library to 5.15.3 was applied on the Apache NiFi 1.6.0 release. Users running a prior 1.x release should upgrade to the appropriate release. |
| CVE-2017-12632 | High | 2018-01-23 | No exploit published | No public exploit | A malicious host header in an incoming HTTP request could cause NiFi to load resources from an external server. The fix to sanitize host headers and compare to a controlled whitelist was applied on the Apache NiFi 1.5.0 release. Users running a prior 1.x release should upgrade to the appropriate release. |
| CVE-2017-5635 | High | 2017-10-19 | No exploit published | No public exploit | In Apache NiFi before 0.7.2 and 1.x before 1.1.2 in a cluster environment, if an anonymous user request is replicated to another node, the originating node identity is used rather than the "anonymous" user. |
| CVE-2017-7667 | High | 2017-06-12 | No exploit published | No public exploit | Apache NiFi before 0.7.4 and 1.x before 1.3.0 need to establish the response header telling browsers to only allow framing with the same origin. |