Oracle Critical Patch Update October 2020
Released October 2020 · Oracle's advisory ↗ · ← Critical Patch Update, July 2020 · Critical Patch Update, January 2021 →
230 CVEs in this release, one square each
By status
26Protected by Waratek8Mitigation candidate100No exploit published3Outside Waratek scope93Not applicable
13Exploited, marked by the ring
No exploit published. For 78 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 106 matches · 11 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
11
10.4%
Rule in development
0
0.0%
Mitigation candidate
1
0.9%
No exploit published
94
88.7%
blocked by ARMR today
11
10.4%
partly blocked
0
0.0%
not blocked
95
89.6%
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
106
100.0%
split by
peak 79 / month
Jul 192
Protected by Waratek1
No exploit published1
Critical1
High1
blocked by ARMR today1
not blocked1
No public exploit2
Aug 191
No exploit published1
High1
not blocked1
No public exploit1
Sep 191
No exploit published1
Medium1
not blocked1
No public exploit1
Oct 198
Protected by Waratek2
No exploit published6
Critical4
High1
Medium3
blocked by ARMR today2
not blocked6
No public exploit8
Nov 190
Dec 190
Jan 200
Feb 200
Mar 203
Mitigation candidate1
No exploit published2
Critical2
Medium1
not blocked3
No public exploit3
Apr 203
No exploit published3
Medium2
Low1
not blocked3
No public exploit3
May 206
Protected by Waratek2
No exploit published4
Critical2
High1
Medium3
blocked by ARMR today2
not blocked4
No public exploit6
Jun 202
Protected by Waratek1
No exploit published1
High2
blocked by ARMR today1
not blocked1
No public exploit2
Jul 201
No exploit published1
Critical1
not blocked1
No public exploit1
Aug 200
Sep 200
Oct 2079
Protected by Waratek5
No exploit published74
Critical7
High27
Medium36
Low9
blocked by ARMR today5
not blocked74
No public exploit79
Aug 19Oct 19Dec 19Feb 20Apr 20Jun 20Aug 20Oct 20
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2019-17267 | Critical | 2019-10-07 | No exploit published | No public exploit | A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10. It is related to net.sf.ehcache.hibernate.EhcacheJtaTransactionManagerLookup. |
| CVE-2019-17091 | Medium | 2019-10-02 | Protected by Waratek | No public exploit | faces/context/PartialViewContextImpl.java in Eclipse Mojarra, as used in Mojarra for Eclipse EE4J before 2.3.10 and Mojarra JavaServer Faces before 2.2.20, allows Reflected XSS because a client window field is mishandled. |
| CVE-2019-3740 | Medium | 2019-09-18 | No exploit published | No public exploit | RSA BSAFE Crypto-J versions prior to 6.2.5 are vulnerable to an Information Exposure Through Timing Discrepancy vulnerabilities during DSA key generation. A malicious remote attacker could potentially exploit those vulnerabilities to recover DSA keys. |
| CVE-2019-12402 | High | 2019-08-30 | No exploit published | No public exploit | The file name encoding algorithm used internally in Apache Commons Compress 1.15 to 1.18 can get into an infinite loop when faced with specially crafted inputs. This can lead to a denial of service attack if an attacker can choose the file names inside of an archive created by Compress. |
| CVE-2019-13990 | Critical | 2019-07-26 | Protected by Waratek | No public exploit | initDocumentParser in xml/XMLSchedulingDataProcessor.java in Terracotta Quartz Scheduler through 2.3.0 allows XXE attacks via a job description. |
| CVE-2018-17196 | High | 2019-07-11 | No exploit published | No public exploit | In Apache Kafka versions between 0.11.0.0 and 2.1.0, it is possible to manually craft a Produce request which bypasses transaction/idempotent ACL validation. Only authenticated clients with Write permission on the respective topics are able to exploit this vulnerability. Users should upgrade to 2.1.1 or later where this vulnerability has been fixed. |