Oracle Critical Patch Update April 2019
Released April 2019 · Oracle's advisory ↗ · ← Critical Patch Update, January 2019 · Critical Patch Update, July 2019 →
207 CVEs in this release, one square each
By status
21Protected by Waratek6Mitigation candidate89No exploit published8Outside Waratek scope83Not applicable
8Exploited, marked by the ring
No exploit published. For 81 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 103 matches · 13 protected · 3 exploited · 1 CISA KEV · 8 public PoC · 3 EPSS ≥ 0.5
Protected by Waratek
14
13.6%
Rule in development
0
0.0%
Mitigation candidate
5
4.9%
No exploit published
84
81.6%
blocked by ARMR today
13
12.6%
partly blocked
1
1.0%
not blocked
89
86.4%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 87 / month
Feb 182
Protected by Waratek1
Mitigation candidate1
Critical1
Medium1
blocked by ARMR today1
not blocked1
Proof of concept only1
No public exploit1
Mar 181
Protected by Waratek1
Critical1
blocked by ARMR today1
No public exploit1
Apr 180
May 182
Protected by Waratek1
No exploit published1
Critical1
High1
blocked by ARMR today1
not blocked1
No public exploit2
Jun 181
No exploit published1
High1
not blocked1
No public exploit1
Jul 180
Aug 181
Protected by Waratek1
High1
blocked by ARMR today1
No public exploit1
Sep 182
Protected by Waratek1
No exploit published1
High2
blocked by ARMR today1
not blocked1
Proof of concept only1
No public exploit1
Oct 182
Mitigation candidate1
No exploit published1
High1
Medium1
not blocked2
Working exploit published1
No public exploit1
Nov 180
Dec 180
Jan 193
Protected by Waratek3
Critical3
blocked by ARMR today3
No public exploit3
Feb 190
Mar 191
Protected by Waratek1
High1
blocked by ARMR today1
No public exploit1
Apr 1987
Protected by Waratek5
Mitigation candidate3
No exploit published79
Critical6
High44
Medium35
Low2
blocked by ARMR today4
partly blocked1
not blocked82
Exploited3
Working exploit published2
No public exploit82
May 191
No exploit published1
Medium1
not blocked1
No public exploit1
Mar 18May 18Jul 18Sep 18Nov 18Jan 19Mar 19May 19
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2018-8088 | Critical | 2018-03-20 | Protected by Waratek | No public exploit | org.slf4j.ext.EventData in the slf4j-ext module in QOS.CH SLF4J before 1.8.0-beta2 allows remote attackers to bypass intended access restrictions via crafted data. EventData in the slf4j-ext module in QOS.CH SLF4J, has been fixed in SLF4J versions 1.7.26 later and in the 2.0.x series. |
| CVE-2018-7489 | Critical | 2018-02-26 | Protected by Waratek | No public exploit | FasterXML jackson-databind before 2.7.9.3, 2.8.x before 2.8.11.1 and 2.9.x before 2.9.5 allows unauthenticated remote code execution because of an incomplete fix for the CVE-2017-7525 deserialization flaw. This is exploitable by sending maliciously crafted JSON input to the readValue method of the ObjectMapper, bypassing a blacklist that is ineffective if the c3p0 libraries are available in the classpath. |
| CVE-2018-1305 | Medium | 2018-02-23 | Mitigation candidate | Proof of concept only | Security constraints defined by annotations of Servlets in Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27, 8.0.0.RC1 to 8.0.49 and 7.0.0 to 7.0.84 were only applied once a Servlet had been loaded. Because security constraints defined in this way apply to the URL pattern and any URLs below that point, it was possible - depending on the order Servlets were loaded - for some security constraints not to be applied. This could have exposed resources to users who were not authorised to access them. |