Oracle Critical Patch Update July 2023
Released July 2023 · Oracle's advisory ↗ · ← Critical Patch Update, April 2023 · Critical Patch Update, October 2023 →
269 CVEs in this release, one square each
By status
45Protected by Waratek5Mitigation candidate105No exploit published31Outside Waratek scope83Not applicable
12Exploited, marked by the ring
No exploit published. For 37 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 207 matches · 117 in Waratek scope · 26 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
207matches
117in Waratek scope56.5%
26protected12.6%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
26
12.6%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
91
44.0%
Outside Waratek scope
26
12.6%
Not applicable
64
30.9%
Withdrawn CVE
0
0.0%
blocked by ARMR today
26
12.6%
partly blocked
0
0.0%
not blocked
181
87.4%
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
207
100.0%
split by
peak 55 / quarter
Q2 181
Protected by Waratek1
Critical1
blocked by ARMR today1
No public exploit1
Q3 181
No exploit published1
Medium1
not blocked1
No public exploit1
Q4 180
Q1 190
Q2 190
Q3 193
Protected by Waratek1
No exploit published1
Outside Waratek scope1
Critical1
High2
blocked by ARMR today1
not blocked2
No public exploit3
Q4 191
No exploit published1
Critical1
not blocked1
No public exploit1
Q1 201
No exploit published1
Critical1
not blocked1
No public exploit1
Q2 200
Q3 201
Protected by Waratek1
Critical1
blocked by ARMR today1
No public exploit1
Q4 205
Protected by Waratek2
No exploit published2
Outside Waratek scope1
High1
Medium3
Low1
blocked by ARMR today2
not blocked3
No public exploit5
Q1 218
Protected by Waratek1
No exploit published6
Not applicable1
Critical2
High4
Medium2
blocked by ARMR today1
not blocked7
No public exploit8
Q2 215
Protected by Waratek3
No exploit published1
Not applicable1
Critical1
High1
Medium3
blocked by ARMR today3
not blocked2
No public exploit5
Q3 218
No exploit published7
Not applicable1
High5
Medium3
not blocked8
No public exploit8
Q4 214
Protected by Waratek2
Outside Waratek scope2
Critical2
Medium2
blocked by ARMR today2
not blocked2
No public exploit4
Q1 227
No exploit published2
Outside Waratek scope1
Not applicable4
High3
Medium4
not blocked7
No public exploit7
Q2 2210
Protected by Waratek4
No exploit published3
Not applicable3
Critical2
High4
Medium3
Low1
blocked by ARMR today4
not blocked6
No public exploit10
Q3 2219
Protected by Waratek1
No exploit published11
Not applicable7
Critical6
High8
Medium4
Low1
blocked by ARMR today1
not blocked18
No public exploit19
Q4 2225
Protected by Waratek5
No exploit published10
Outside Waratek scope1
Not applicable9
Critical3
High19
Medium3
blocked by ARMR today5
not blocked20
No public exploit25
Q1 2337
Protected by Waratek3
No exploit published13
Outside Waratek scope1
Not applicable20
Critical2
High18
Medium16
Low1
blocked by ARMR today3
not blocked34
No public exploit37
Q2 2316
Protected by Waratek1
No exploit published8
Not applicable7
Critical2
High5
Medium9
blocked by ARMR today1
not blocked15
No public exploit16
Q3 2355
Protected by Waratek1
No exploit published24
Outside Waratek scope19
Not applicable11
Critical2
High5
Medium37
Low11
blocked by ARMR today1
not blocked54
No public exploit55
Q3 18Q1 19Q3 19Q1 20Q3 20Q1 21Q3 21Q1 22Q3 22Q1 23Q3 23
| 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-2019-17531 | Critical | 2019-10-12 | No exploit published | No public exploit | A Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.0.0 through 2.9.10. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the apache-log4j-extra (version 1.2.x) jar in the classpath, and an attacker can provide a JNDI service to access, it is possible to make the service execute a malicious payload. |
| 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-10086 | High | 2019-08-20 | Protected by Waratek | No public exploit | In Apache Commons Beanutils 1.9.2, a special BeanIntrospector class was added which allows suppressing the ability for an attacker to access the classloader via the class property available on all Java objects. We, however were not using this by default characteristic of the PropertyUtilsBean. |
| CVE-2019-13990 | Critical | 2019-07-26 | Outside Waratek scope | 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-8032 | Medium | 2018-08-02 | No exploit published | No public exploit | Apache Axis 1.x up to and including 1.4 is vulnerable to a cross-site scripting (XSS) attack in the default servlet/services. |
| CVE-2018-1282 | Critical | 2018-04-05 | Protected by Waratek | No public exploit | This vulnerability in Apache Hive JDBC driver 0.7.1 to 2.3.2 allows carefully crafted arguments to be used to bypass the argument escaping/cleanup that JDBC driver does in PreparedStatement implementation. |