Oracle Critical Patch Update October 2024
Released October 2024 · Oracle's advisory ↗ · ← Critical Patch Update, July 2024 · Critical Patch Update, January 2025 →
278 CVEs in this release, one square each
By status
15Protected by Waratek3Mitigation candidate88No exploit published26Outside Waratek scope144Not applicable2Withdrawn CVE
13Exploited, marked by the ring
No exploit published. For 51 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 101 matches · 11 protected · 4 exploited · 1 CISA KEV · 6 public PoC · 4 EPSS ≥ 0.5
Protected by Waratek
11
10.9%
Rule in development
0
0.0%
Mitigation candidate
3
3.0%
No exploit published
87
86.1%
blocked by ARMR today
11
10.9%
partly blocked
0
0.0%
not blocked
90
89.1%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
4
4.0%
Working exploit published
0
0.0%
Proof of concept only
7
6.9%
Forecast only
2
2.0%
No public exploit
88
87.1%
split by
peak 49 / quarter
Q1 224
Protected by Waratek3
No exploit published1
Critical1
High2
Medium1
blocked by ARMR today3
not blocked1
Proof of concept only1
Forecast only2
No public exploit1
Q2 220
Q3 220
Q4 220
Q1 231
Protected by Waratek1
High1
blocked by ARMR today1
Exploited1
Q2 233
No exploit published3
High1
Medium2
not blocked3
No public exploit3
Q3 235
Protected by Waratek1
No exploit published4
High3
Medium2
blocked by ARMR today1
not blocked4
No public exploit5
Q4 236
Mitigation candidate1
No exploit published5
Critical1
High3
Medium2
not blocked6
Exploited1
No public exploit5
Q1 2414
Mitigation candidate1
No exploit published13
Critical1
High6
Medium7
not blocked14
Proof of concept only4
No public exploit10
Q2 244
Protected by Waratek1
Mitigation candidate1
No exploit published2
High4
blocked by ARMR today1
not blocked3
Exploited1
No public exploit3
Q3 2415
Protected by Waratek3
No exploit published12
Critical1
High10
Medium4
blocked by ARMR today3
not blocked12
Exploited1
Proof of concept only2
No public exploit12
Q4 2449
Protected by Waratek2
No exploit published47
Critical2
High30
Medium12
Low5
blocked by ARMR today2
not blocked47
No public exploit49
Q1 22Q2 22Q3 22Q4 22Q1 23Q2 23Q3 23Q4 23Q1 24Q2 24Q3 24Q4 24
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-23302 | High | 2022-01-18 | Protected by Waratek | Forecast only | JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions. |