Oracle Critical Patch Update April 2017
Released April 2017 · Oracle's advisory ↗ · ← Critical Patch Update, January 2017 · Critical Patch Update, July 2017 →
227 CVEs in this release, one square each
By status
17Protected by Waratek1Mitigation candidate95No exploit published13Outside Waratek scope101Not applicable
8Exploited, marked by the ring
No exploit published. For 93 of them, Oracle's security advisory is the source of public detail.
Protected by Waratek. Waratek RASP can block exploitation of these on systems that have not applied the patch yet.
Overview 101 matches · 0 in Waratek scope · 0 protected · 3 exploited · 0 CISA KEV · 12 public PoC · 5 EPSS ≥ 0.5
101matches
0in Waratek scope0.0%
0protected0.0%
3exploited3.0%
0CISA KEV0.0%
12public PoC11.9%
5EPSS ≥ 0.55.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
0
0.0%
Not applicable
101
100.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
101
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
3
3.0%
Working exploit published
9
8.9%
Proof of concept only
0
0.0%
Forecast only
2
2.0%
No public exploit
87
86.1%
split by
peak 84 / year
20091
Not applicable1
Critical1
not blocked1
Working exploit published1
20100
20110
20122
Not applicable2
High1
Medium1
not blocked2
No public exploit2
20132
Not applicable2
High1
Medium1
not blocked2
No public exploit2
20140
20153
Not applicable3
High1
Medium2
not blocked3
Exploited1
No public exploit2
20169
Not applicable9
Critical4
High3
Medium2
not blocked9
Working exploit published1
Forecast only1
No public exploit7
201784
Not applicable84
Critical3
High46
Medium26
Low9
not blocked84
Exploited2
Working exploit published7
Forecast only1
No public exploit74
200920102011201220132014201520162017
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2004-2761 | Critical | 2009-01-05 | Not applicable | Working exploit published | The MD5 Message-Digest Algorithm is not collision resistant, which makes it easier for context-dependent attackers to conduct spoofing attacks, as demonstrated by attacks on the use of MD5 in the signature algorithm of an X.509 certificate. |