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 102 matches · 0 protected · 3 exploited · 1 CISA KEV · 5 public PoC · 6 EPSS ≥ 0.5
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
6
5.9%
No exploit published
96
94.1%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
102
100.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 74 / month
May 191
No exploit published1
Medium1
not blocked1
No public exploit1
Jun 191
No exploit published1
High1
not blocked1
Forecast only1
Jul 191
No exploit published1
High1
not blocked1
No public exploit1
Aug 191
No exploit published1
High1
not blocked1
No public exploit1
Sep 191
No exploit published1
Medium1
not blocked1
No public exploit1
Oct 196
No exploit published6
Critical4
High1
Medium1
not blocked6
No public exploit6
Nov 190
Dec 190
Jan 201
Mitigation candidate1
High1
not blocked1
Proof of concept only1
Feb 200
Mar 203
Mitigation candidate1
No exploit published2
Critical2
Medium1
not blocked3
No public exploit3
Apr 205
Mitigation candidate2
No exploit published3
Medium4
Low1
not blocked5
Exploited2
No public exploit3
May 204
No exploit published4
High1
Medium3
not blocked4
No public exploit4
Jun 201
No exploit published1
High1
not blocked1
No public exploit1
Jul 202
Mitigation candidate1
No exploit published1
Critical1
High1
not blocked2
Working exploit published1
No public exploit1
Aug 201
Mitigation candidate1
Critical1
not blocked1
Exploited1
Sep 200
Oct 2074
No exploit published74
Critical5
High27
Medium35
Low7
not blocked74
No public exploit74
Jun 19Aug 19Oct 19Dec 19Feb 20Apr 20Jun 20Aug 20Oct 20
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2019-10072 | High | 2019-06-21 | No exploit published | Forecast only | The fix for CVE-2019-0199 was incomplete and did not address HTTP/2 connection window exhaustion on write in Apache Tomcat versions 9.0.0.M1 to 9.0.19 and 8.5.0 to 8.5.40 . By not sending WINDOW_UPDATE messages for the connection window (stream 0) clients were able to cause server-side threads to block eventually leading to thread exhaustion and a DoS. |
| CVE-2019-0201 | Medium | 2019-05-23 | No exploit published | No public exploit | An issue is present in Apache ZooKeeper 1.0.0 to 3.4.13 and 3.5.0-alpha to 3.5.4-beta. ZooKeeper’s getACL() command doesn’t check any permission when retrieves the ACLs of the requested node and returns all information contained in the ACL Id field as plaintext string. DigestAuthenticationProvider overloads the Id field with the hash value that is used for user authentication. As a consequence, if Digest Authentication is in use, the unsalted hash value will be disclosed by getACL() request for unauthenticated or unprivileged users. |