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 103 matches · 13 protected · 7 exploited · 5 CISA KEV · 9 public PoC · 9 EPSS ≥ 0.5
Protected by Waratek
13
12.6%
Rule in development
0
0.0%
Mitigation candidate
5
4.9%
No exploit published
85
82.5%
blocked by ARMR today
13
12.6%
partly blocked
0
0.0%
not blocked
90
87.4%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
7
6.8%
Working exploit published
2
1.9%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
94
91.3%
split by
peak 82 / month
Feb 201
Protected by Waratek1
Critical1
blocked by ARMR today1
Exploited1
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 207
Protected by Waratek3
No exploit published4
Critical2
High2
Medium3
blocked by ARMR today3
not blocked4
Working exploit published1
No public exploit6
Jun 202
Protected by Waratek1
No exploit published1
High2
blocked by ARMR today1
not blocked1
No public exploit2
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 2082
Protected by Waratek8
No exploit published74
Critical8
High29
Medium36
Low9
blocked by ARMR today8
not blocked74
Exploited3
No public exploit79
Feb 20Mar 20Apr 20May 20Jun 20Jul 20Aug 20Sep 20Oct 20
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2020-1953 | Critical | 2020-03-13 | No exploit published | No public exploit | Apache Commons Configuration uses a third-party library to parse YAML files which by default allows the instantiation of classes if the YAML includes special statements. Apache Commons Configuration versions 2.2, 2.3, 2.4, 2.5, 2.6 did not change the default settings of this library. So if a YAML file was loaded from an untrusted source, it could therefore load and execute code out of the control of the host application. |
| CVE-2020-9546 | Critical | 2020-03-02 | Mitigation candidate | No public exploit | FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.hadoop.shaded.com.zaxxer.hikari.HikariConfig (aka shaded hikari-config). |
| CVE-2020-1938 | Critical | 2020-02-24 | Protected by Waratek | Exploited | When using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to Apache Tomcat. Tomcat treats AJP connections as having higher trust than, for example, a similar HTTP connection. If such connections are available to an attacker, they can be exploited in ways that may be surprising. In Apache Tomcat 9.0.0.M1 to 9.0.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99, Tomcat shipped with an AJP Connector enabled by default that listened on all configured IP addresses. It was expected (and recommended in the security guide) that this Connector would be disabled if not required. This vulnerability report identified a mechanism that allowed: - returning arbitrary files from anywhere in the web application - processing any file in the web application as a JSP Further, if the web application allowed file upload and stored those files within the web application (or the attacker was able to control the content of the web application by some other means) then this, along with the ability to process a file as a JSP, made remote code execution possible. It is important to note that mitigation is only required if an AJP port is accessible to untrusted users. Users wishing to take a defence-in-depth approach and block the vector that permits returning arbitrary files and execution as JSP may upgrade to Apache Tomcat 9.0.31, 8.5.51 or 7.0.100 or later. A number of changes were made to the default AJP Connector configuration in 9.0.31 to harden the default configuration. It is likely that users upgrading to 9.0.31, 8.5.51 or 7.0.100 or later will need to make small changes to their configurations. |