Oracle Critical Patch Update October 2023
Released October 2023 · Oracle's advisory ↗ · ← Critical Patch Update, July 2023 · Critical Patch Update, January 2024 →
245 CVEs in this release, one square each
By status
16Protected by Waratek7Mitigation candidate91No exploit published6Outside Waratek scope125Not applicable
8Exploited, marked by the ring
No exploit published. For 35 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 · 54 in Waratek scope · 13 protected · 5 exploited · 1 CISA KEV · 8 public PoC · 7 EPSS ≥ 0.5
102matches
54in Waratek scope52.9%
13protected12.7%
5exploited4.9%
1CISA KEV1.0%
8public PoC7.8%
7EPSS ≥ 0.56.9%
Protected by Waratek
13
12.7%
Rule in development
0
0.0%
Mitigation candidate
5
4.9%
No exploit published
36
35.3%
Outside Waratek scope
3
2.9%
Not applicable
45
44.1%
Withdrawn CVE
0
0.0%
blocked by ARMR today
13
12.7%
partly blocked
0
0.0%
not blocked
89
87.3%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
5
4.9%
Working exploit published
0
0.0%
Proof of concept only
28
27.5%
Forecast only
2
2.0%
No public exploit
67
65.7%
split by
peak 29 / quarter
Q2 191
Mitigation candidate1
Medium1
not blocked1
Exploited1
Q3 191
Protected by Waratek1
High1
blocked by ARMR today1
No public exploit1
Q4 191
Outside Waratek scope1
High1
not blocked1
No public exploit1
Q1 201
No exploit published1
Critical1
not blocked1
No public exploit1
Q2 202
Mitigation candidate2
Medium2
not blocked2
Exploited2
Q3 202
Not applicable2
High2
not blocked2
No public exploit2
Q4 202
No exploit published2
High1
Medium1
not blocked2
No public exploit2
Q1 214
No exploit published3
Not applicable1
High2
Medium2
not blocked4
No public exploit4
Q2 211
No exploit published1
High1
not blocked1
Forecast only1
Q3 214
No exploit published4
High2
Medium2
not blocked4
No public exploit4
Q4 216
Protected by Waratek1
Mitigation candidate1
No exploit published2
Not applicable2
High3
Medium3
blocked by ARMR today1
not blocked5
Proof of concept only1
No public exploit5
Q1 224
No exploit published2
Not applicable2
High3
Medium1
not blocked4
No public exploit4
Q2 2215
Protected by Waratek5
No exploit published3
Not applicable7
Critical4
High8
Medium3
blocked by ARMR today5
not blocked10
Proof of concept only3
No public exploit12
Q3 228
Protected by Waratek3
Mitigation candidate1
No exploit published2
Outside Waratek scope1
Not applicable1
Critical3
High3
Medium2
blocked by ARMR today3
not blocked5
Proof of concept only7
No public exploit1
Q4 2221
Protected by Waratek3
No exploit published9
Outside Waratek scope1
Not applicable8
Critical3
High14
Medium3
Low1
blocked by ARMR today3
not blocked18
Exploited1
Proof of concept only8
No public exploit12
Q1 2329
No exploit published7
Not applicable22
Critical3
High15
Medium11
not blocked29
Exploited1
Proof of concept only9
Forecast only1
No public exploit18
Q3 19Q1 20Q3 20Q1 21Q3 21Q1 22Q3 22Q1 23
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| 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-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. |