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 Waratek6Mitigation candidate93No exploit published4Outside Waratek scope158Not applicable2Withdrawn CVE
13Exploited, marked by the ring
No exploit published. For 50 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 108 matches · 13 protected · 4 exploited · 1 CISA KEV · 7 public PoC · 4 EPSS ≥ 0.5
Protected by Waratek
13
12.0%
Rule in development
0
0.0%
Mitigation candidate
4
3.7%
No exploit published
91
84.3%
blocked by ARMR today
13
12.0%
partly blocked
0
0.0%
not blocked
95
88.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
4
3.7%
Working exploit published
0
0.0%
Proof of concept only
8
7.4%
Forecast only
2
1.9%
No public exploit
94
87.0%
split by
peak 48 / quarter
Q2 212
Protected by Waratek1
No exploit published1
Critical1
Medium1
blocked by ARMR today1
not blocked1
No public exploit2
Q3 210
Q4 215
Protected by Waratek1
Mitigation candidate1
No exploit published3
High2
Medium3
blocked by ARMR today1
not blocked4
Proof of concept only1
No public exploit4
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 2416
Protected by Waratek3
No exploit published13
Critical1
High10
Medium5
blocked by ARMR today3
not blocked13
Exploited1
Proof of concept only2
No public exploit13
Q4 2448
Protected by Waratek2
No exploit published46
Critical2
High30
Medium11
Low5
blocked by ARMR today2
not blocked46
No public exploit48
Q2 21Q4 21Q2 22Q4 22Q2 23Q4 23Q2 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. |
| CVE-2021-41184 | Medium | 2021-10-26 | Mitigation candidate | Proof of concept only | jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of the `of` option of the `.position()` util from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `of` option is now treated as a CSS selector. A workaround is to not accept the value of the `of` option from untrusted sources. |
| CVE-2021-41183 | Medium | 2021-10-26 | No exploit published | No public exploit | jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of various `*Text` options of the Datepicker widget from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. The values passed to various `*Text` options are now always treated as pure text, not HTML. A workaround is to not accept the value of the `*Text` options from untrusted sources. |
| CVE-2021-41182 | Medium | 2021-10-26 | No exploit published | No public exploit | jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of the `altField` option of the Datepicker widget from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `altField` option is now treated as a CSS selector. A workaround is to not accept the value of the `altField` option from untrusted sources. |
| CVE-2021-37137 | High | 2021-10-19 | No exploit published | No public exploit | The Snappy frame decoder function doesn't restrict the chunk length which may lead to excessive memory usage. Beside this it also may buffer reserved skippable chunks until the whole chunk was received which may lead to excessive memory usage as well. This vulnerability can be triggered by supplying malicious input that decompresses to a very big size (via a network stream or a file) or by sending a huge skippable chunk. |
| CVE-2021-37136 | High | 2021-10-19 | Protected by Waratek | No public exploit | The Bzip2 decompression decoder function doesn't allow setting size restrictions on the decompressed output data (which affects the allocation size used during decompression). All users of Bzip2Decoder are affected. The malicious input can trigger an OOME and so a DoS attack |
| CVE-2020-9493 | Critical | 2021-06-16 | Protected by Waratek | No public exploit | A deserialization flaw was found in Apache Chainsaw versions prior to 2.1.0 which could lead to malicious code execution. |
| CVE-2021-28170 | Medium | 2021-05-26 | No exploit published | No public exploit | In the Jakarta Expression Language implementation 3.0.3 and earlier, a bug in the ELParserTokenManager enables invalid EL expressions to be evaluated as if they were valid. |