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 209 matches · 82 in Waratek scope · 6 protected · 7 exploited · 3 CISA KEV · 12 public PoC · 9 EPSS ≥ 0.5
209matches
82in Waratek scope39.2%
6protected2.9%
7exploited3.3%
3CISA KEV1.4%
12public PoC5.7%
9EPSS ≥ 0.54.3%
Protected by Waratek
6
2.9%
Rule in development
0
0.0%
Mitigation candidate
2
1.0%
No exploit published
74
35.4%
Outside Waratek scope
2
1.0%
Not applicable
123
58.9%
Withdrawn CVE
2
1.0%
blocked by ARMR today
6
2.9%
partly blocked
0
0.0%
not blocked
203
97.1%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 85 / month
Jan 246
Not applicable6
Critical1
High1
Medium4
not blocked6
No public exploit6
Feb 2415
No exploit published5
Not applicable10
Critical2
High10
Medium3
not blocked15
Proof of concept only2
No public exploit13
Mar 2421
Mitigation candidate1
No exploit published8
Not applicable11
Withdrawn CVE1
Critical1
High10
Medium9
Unknown1
not blocked21
Proof of concept only5
No public exploit16
Apr 2412
Protected by Waratek1
Not applicable11
Critical1
High7
Medium4
blocked by ARMR today1
not blocked11
Exploited1
Proof of concept only3
Forecast only2
No public exploit6
May 2414
Mitigation candidate1
No exploit published1
Not applicable12
High7
Medium7
not blocked14
Exploited2
Proof of concept only1
No public exploit11
Jun 2411
No exploit published1
Outside Waratek scope1
Not applicable9
Critical3
High3
Medium5
not blocked11
Exploited1
Proof of concept only3
No public exploit7
Jul 2426
No exploit published8
Not applicable17
Withdrawn CVE1
Critical6
High12
Medium6
Low1
Unknown1
not blocked26
Exploited2
Working exploit published2
Proof of concept only4
No public exploit18
Aug 2410
Protected by Waratek2
No exploit published3
Not applicable5
Critical3
High2
Medium4
Low1
blocked by ARMR today2
not blocked8
Proof of concept only1
No public exploit9
Sep 247
Protected by Waratek1
No exploit published2
Not applicable4
High5
Medium1
Low1
blocked by ARMR today1
not blocked6
Exploited1
Forecast only1
No public exploit5
Oct 2485
Protected by Waratek2
No exploit published46
Outside Waratek scope1
Not applicable36
Critical2
High32
Medium36
Low15
blocked by ARMR today2
not blocked83
No public exploit85
Nov 241
Not applicable1
Critical1
not blocked1
No public exploit1
Dec 240
Jan 251
Not applicable1
Low1
not blocked1
No public exploit1
Jan 24Mar 24May 24Jul 24Sep 24Nov 24Jan 25
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2024-25062 | High | 2024-02-04 | Not applicable | No public exploit | An issue was discovered in libxml2 before 2.11.7 and 2.12.x before 2.12.5. When using the XML Reader interface with DTD validation and XInclude expansion enabled, processing crafted XML documents can lead to an xmlValidatePopElement use-after-free. |
| CVE-2024-23635 | Medium | 2024-02-02 | No exploit published | No public exploit | AntiSamy is a library for performing fast, configurable cleansing of HTML coming from untrusted sources. Prior to 1.7.5, there is a potential for a mutation XSS (mXSS) vulnerability in AntiSamy caused by flawed parsing of the HTML being sanitized. To be subject to this vulnerability the `preserveComments` directive must be enabled in your policy file. As a result, certain crafty inputs can result in elements in comment tags being interpreted as executable when using AntiSamy's sanitized output. Patched in AntiSamy 1.7.5 and later. |
| CVE-2022-34381 | Critical | 2024-02-02 | Not applicable | No public exploit | Dell BSAFE SSL-J version 7.0 and all versions prior to 6.5, and Dell BSAFE Crypto-J versions prior to 6.2.6.1 contain an unmaintained third-party component vulnerability. An unauthenticated remote attacker could potentially exploit this vulnerability, leading to the compromise of the impacted system. This is a Critical vulnerability and Dell recommends customers to upgrade at the earliest opportunity. |
| CVE-2024-0727 | Medium | 2024-01-26 | Not applicable | No public exploit | Issue summary: Processing a maliciously formatted PKCS12 file may lead OpenSSL to crash leading to a potential Denial of Service attack Impact summary: Applications loading files in the PKCS12 format from untrusted sources might terminate abruptly. A file in PKCS12 format can contain certificates and keys and may come from an untrusted source. The PKCS12 specification allows certain fields to be NULL, but OpenSSL does not correctly check for this case. This can lead to a NULL pointer dereference that results in OpenSSL crashing. If an application processes PKCS12 files from an untrusted source using the OpenSSL APIs then that application will be vulnerable to this issue. OpenSSL APIs that are vulnerable to this are: PKCS12_parse(), PKCS12_unpack_p7data(), PKCS12_unpack_p7encdata(), PKCS12_unpack_authsafes() and PKCS12_newpass(). We have also fixed a similar issue in SMIME_write_PKCS7(). However since this function is related to writing data we do not consider it security significant. The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. |
| CVE-2023-50447 | High | 2024-01-19 | Not applicable | No public exploit | Pillow through 10.1.0 allows PIL.ImageMath.eval Arbitrary Code Execution via the environment parameter, a different vulnerability than CVE-2022-22817 (which was about the expression parameter). |
| CVE-2023-6816 | Critical | 2024-01-18 | Not applicable | No public exploit | A flaw was found in X.Org server. Both DeviceFocusEvent and the XIQueryPointer reply contain a bit for each logical button currently down. Buttons can be arbitrarily mapped to any value up to 255, but the X.Org Server was only allocating space for the device's particular number of buttons, leading to a heap overflow if a bigger value was used. |
| CVE-2024-0232 | Medium | 2024-01-16 | Not applicable | No public exploit | A heap use-after-free issue has been identified in SQLite in the jsonParseAddNodeArray() function in sqlite3.c. This flaw allows a local attacker to leverage a victim to pass specially crafted malicious input to the application, potentially causing a crash and leading to a denial of service. |
| CVE-2023-6129 | Medium | 2024-01-09 | Not applicable | No public exploit | Issue summary: The POLY1305 MAC (message authentication code) implementation contains a bug that might corrupt the internal state of applications running on PowerPC CPU based platforms if the CPU provides vector instructions. Impact summary: If an attacker can influence whether the POLY1305 MAC algorithm is used, the application state might be corrupted with various application dependent consequences. The POLY1305 MAC (message authentication code) implementation in OpenSSL for PowerPC CPUs restores the contents of vector registers in a different order than they are saved. Thus the contents of some of these vector registers are corrupted when returning to the caller. The vulnerable code is used only on newer PowerPC processors supporting the PowerISA 2.07 instructions. The consequences of this kind of internal application state corruption can be various - from no consequences, if the calling application does not depend on the contents of non-volatile XMM registers at all, to the worst consequences, where the attacker could get complete control of the application process. However unless the compiler uses the vector registers for storing pointers, the most likely consequence, if any, would be an incorrect result of some application dependent calculations or a crash leading to a denial of service. The POLY1305 MAC algorithm is most frequently used as part of the CHACHA20-POLY1305 AEAD (authenticated encryption with associated data) algorithm. The most common usage of this AEAD cipher is with TLS protocol versions 1.2 and 1.3. If this cipher is enabled on the server a malicious client can influence whether this AEAD cipher is used. This implies that TLS server applications using OpenSSL can be potentially impacted. However we are currently not aware of any concrete application that would be affected by this issue therefore we consider this a Low severity security issue. |
| CVE-2023-6004 | Medium | 2024-01-03 | Not applicable | No public exploit | A flaw was found in libssh. By utilizing the ProxyCommand or ProxyJump feature, users can exploit unchecked hostname syntax on the client. This issue may allow an attacker to inject malicious code into the command of the features mentioned through the hostname parameter. |