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 104 matches · 0 protected · 4 exploited · 1 CISA KEV · 6 public PoC · 7 EPSS ≥ 0.5
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
7
6.7%
No exploit published
97
93.3%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
104
100.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 74 / quarter
Q2 194
Mitigation candidate1
No exploit published3
High1
Medium3
not blocked4
Exploited1
Forecast only1
No public exploit2
Q3 193
No exploit published3
High2
Medium1
not blocked3
No public exploit3
Q4 196
No exploit published6
Critical4
High1
Medium1
not blocked6
No public exploit6
Q1 204
Mitigation candidate2
No exploit published2
Critical2
High1
Medium1
not blocked4
Proof of concept only1
No public exploit3
Q2 2010
Mitigation candidate2
No exploit published8
High2
Medium7
Low1
not blocked10
Exploited2
No public exploit8
Q3 203
Mitigation candidate2
No exploit published1
Critical2
High1
not blocked3
Exploited1
Working exploit published1
No public exploit1
Q4 2074
No exploit published74
Critical5
High27
Medium35
Low7
not blocked74
No public exploit74
Q2 19Q3 19Q4 19Q1 20Q2 20Q3 20Q4 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. |
| CVE-2019-10247 | Medium | 2019-04-22 | No exploit published | No public exploit | In Eclipse Jetty version 7.x, 8.x, 9.2.27 and older, 9.3.26 and older, and 9.4.16 and older, the server running on any OS and Jetty version combination will reveal the configured fully qualified directory base resource location on the output of the 404 error for not finding a Context that matches the requested path. The default server behavior on jetty-distribution and jetty-home will include at the end of the Handler tree a DefaultHandler, which is responsible for reporting this 404 error, it presents the various configured contexts as HTML for users to click through to. This produced HTML includes output that contains the configured fully qualified directory base resource location for each context. |
| CVE-2019-11358 | Medium | 2019-04-20 | Mitigation candidate | Exploited | jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype. |