Oracle Critical Patch Update January 2025
Released January 2025 · Oracle's advisory ↗ · ← Critical Patch Update, October 2024 · Critical Patch Update, April 2025 →
253 CVEs in this release, one square each
By status
14Protected by Waratek3Mitigation candidate92No exploit published3Outside Waratek scope141Not applicable
11Exploited, marked by the ring
No exploit published. For 48 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 208 matches · 88 in Waratek scope · 7 protected · 9 exploited · 1 CISA KEV · 15 public PoC · 9 EPSS ≥ 0.5
208matches
88in Waratek scope42.3%
7protected3.4%
9exploited4.3%
1CISA KEV0.5%
15public PoC7.2%
9EPSS ≥ 0.54.3%
Protected by Waratek
7
3.4%
Rule in development
0
0.0%
Mitigation candidate
2
1.0%
No exploit published
79
38.0%
Outside Waratek scope
3
1.4%
Not applicable
117
56.2%
Withdrawn CVE
0
0.0%
blocked by ARMR today
7
3.4%
partly blocked
0
0.0%
not blocked
201
96.6%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 84 / month
Nov 237
No exploit published1
Not applicable6
Critical1
High1
Medium5
not blocked7
No public exploit7
Dec 234
No exploit published1
Not applicable3
Medium4
not blocked4
Exploited1
Proof of concept only2
No public exploit1
Jan 244
Not applicable4
Medium4
not blocked4
No public exploit4
Feb 2411
No exploit published5
Outside Waratek scope1
Not applicable5
Critical1
High7
Medium3
not blocked11
Proof of concept only3
No public exploit8
Mar 2413
Mitigation candidate1
No exploit published4
Not applicable8
High5
Medium8
not blocked13
Proof of concept only4
No public exploit9
Apr 248
No exploit published1
Not applicable7
High6
Medium2
not blocked8
Exploited1
Proof of concept only2
Forecast only1
No public exploit4
May 2416
No exploit published5
Not applicable11
Critical1
High8
Medium7
not blocked16
Proof of concept only1
No public exploit15
Jun 248
No exploit published1
Outside Waratek scope1
Not applicable6
Critical2
High5
Medium1
not blocked8
Exploited1
No public exploit7
Jul 2411
No exploit published3
Not applicable8
Critical3
High6
Medium1
Low1
not blocked11
Exploited1
Working exploit published1
Proof of concept only2
No public exploit7
Aug 249
Protected by Waratek1
No exploit published1
Not applicable7
Critical3
High2
Medium4
blocked by ARMR today1
not blocked8
Proof of concept only1
No public exploit8
Sep 249
Protected by Waratek1
No exploit published2
Not applicable6
High6
Medium2
Low1
blocked by ARMR today1
not blocked8
Exploited1
Forecast only1
No public exploit7
Oct 2413
Protected by Waratek1
No exploit published7
Not applicable5
Critical1
High2
Medium9
Low1
blocked by ARMR today1
not blocked12
Exploited1
Proof of concept only2
No public exploit10
Nov 243
No exploit published2
Not applicable1
Critical1
High1
Medium1
not blocked3
Proof of concept only1
No public exploit2
Dec 247
Protected by Waratek3
Mitigation candidate1
No exploit published2
Not applicable1
Critical3
High1
Medium2
Low1
blocked by ARMR today3
not blocked4
Exploited2
Working exploit published1
Proof of concept only2
No public exploit2
Jan 2584
Protected by Waratek1
No exploit published44
Not applicable39
Critical4
High12
Medium65
Low3
blocked by ARMR today1
not blocked83
Exploited1
No public exploit83
Feb 251
Outside Waratek scope1
High1
not blocked1
No public exploit1
Dec 23Feb 24Apr 24Jun 24Aug 24Oct 24Dec 24Feb 25
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2023-46218 | Medium | 2023-12-07 | Not applicable | Proof of concept only | This flaw allows a malicious HTTP server to set "super cookies" in curl that are then passed back to more origins than what is otherwise allowed or possible. This allows a site to set cookies that then would get sent to different and unrelated sites and domains. It could do this by exploiting a mixed case flaw in curl's function that verifies a given cookie domain against the Public Suffix List (PSL). For example a cookie could be set with `domain=co.UK` when the URL used a lower case hostname `curl.co.uk`, even though `co.uk` is listed as a PSL domain. |
| CVE-2023-5981 | Medium | 2023-11-28 | Not applicable | No public exploit | A vulnerability was found that the response times to malformed ciphertexts in RSA-PSK ClientKeyExchange differ from response times of ciphertexts with correct PKCS#1 v1.5 padding. |
| CVE-2023-33202 | Medium | 2023-11-23 | No exploit published | No public exploit | Bouncy Castle for Java before 1.73 contains a potential Denial of Service (DoS) issue within the Bouncy Castle org.bouncycastle.openssl.PEMParser class. This class parses OpenSSL PEM encoded streams containing X.509 certificates, PKCS8 encoded keys, and PKCS7 objects. Parsing a file that has crafted ASN.1 data through the PEMParser causes an OutOfMemoryError, which can enable a denial of service attack. (For users of the FIPS Java API: BC-FJA 1.0.2.3 and earlier are affected; BC-FJA 1.0.2.4 is fixed.) |
| CVE-2023-26031 | High | 2023-11-16 | Not applicable | No public exploit | Relative library resolution in linux container-executor binary in Apache Hadoop 3.3.1-3.3.4 on Linux allows local user to gain root privileges. If the YARN cluster is accepting work from remote (authenticated) users, this MAY permit remote users to gain root privileges. Hadoop 3.3.0 updated the " YARN Secure Containers https://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/SecureContainer.html " to add a feature for executing user-submitted applications in isolated linux containers. The native binary HADOOP_HOME/bin/container-executor is used to launch these containers; it must be owned by root and have the suid bit set in order for the YARN processes to run the containers as the specific users submitting the jobs. The patch " YARN-10495 https://issues.apache.org/jira/browse/YARN-10495 . make the rpath of container-executor configurable" modified the library loading path for loading .so files from "$ORIGIN/" to ""$ORIGIN/:../lib/native/". This is the a path through which libcrypto.so is located. Thus it is is possible for a user with reduced privileges to install a malicious libcrypto library into a path to which they have write access, invoke the container-executor command, and have their modified library executed as root. If the YARN cluster is accepting work from remote (authenticated) users, and these users' submitted job are executed in the physical host, rather than a container, then the CVE permits remote users to gain root privileges. The fix for the vulnerability is to revert the change, which is done in YARN-11441 https://issues.apache.org/jira/browse/YARN-11441 , "Revert YARN-10495". This patch is in hadoop-3.3.5. To determine whether a version of container-executor is vulnerable, use the readelf command. If the RUNPATH or RPATH value contains the relative path "./lib/native/" then it is at risk $ readelf -d container-executor|grep 'RUNPATH\|RPATH' 0x000000000000001d (RUNPATH) Library runpath: [$ORIGIN/:../lib/native/] If it does not, then it is safe: $ readelf -d container-executor|grep 'RUNPATH\|RPATH' 0x000000000000001d (RUNPATH) Library runpath: [$ORIGIN/] For an at-risk version of container-executor to enable privilege escalation, the owner must be root and the suid bit must be set $ ls -laF /opt/hadoop/bin/container-executor ---Sr-s---. 1 root hadoop 802968 May 9 20:21 /opt/hadoop/bin/container-executor A safe installation lacks the suid bit; ideally is also not owned by root. $ ls -laF /opt/hadoop/bin/container-executor -rwxr-xr-x. 1 yarn hadoop 802968 May 9 20:21 /opt/hadoop/bin/container-executor This configuration does not support Yarn Secure Containers, but all other hadoop services, including YARN job execution outside secure containers continue to work. |
| CVE-2023-5678 | Medium | 2023-11-06 | Not applicable | No public exploit | Issue summary: Generating excessively long X9.42 DH keys or checking excessively long X9.42 DH keys or parameters may be very slow. Impact summary: Applications that use the functions DH_generate_key() to generate an X9.42 DH key may experience long delays. Likewise, applications that use DH_check_pub_key(), DH_check_pub_key_ex() or EVP_PKEY_public_check() to check an X9.42 DH key or X9.42 DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service. While DH_check() performs all the necessary checks (as of CVE-2023-3817), DH_check_pub_key() doesn't make any of these checks, and is therefore vulnerable for excessively large P and Q parameters. Likewise, while DH_generate_key() performs a check for an excessively large P, it doesn't check for an excessively large Q. An application that calls DH_generate_key() or DH_check_pub_key() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack. DH_generate_key() and DH_check_pub_key() are also called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_pub_key_ex(), EVP_PKEY_public_check(), and EVP_PKEY_generate(). Also vulnerable are the OpenSSL pkey command line application when using the "-pubcheck" option, as well as the OpenSSL genpkey command line application. The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue. |
| CVE-2023-42669 | Medium | 2023-11-06 | Not applicable | No public exploit | A vulnerability was found in Samba's "rpcecho" development server, a non-Windows RPC server used to test Samba's DCE/RPC stack elements. This vulnerability stems from an RPC function that can be blocked indefinitely. The issue arises because the "rpcecho" service operates with only one worker in the main RPC task, allowing calls to the "rpcecho" server to be blocked for a specified time, causing service disruptions. This disruption is triggered by a "sleep()" call in the "dcesrv_echo_TestSleep()" function under specific conditions. Authenticated users or attackers can exploit this vulnerability to make calls to the "rpcecho" server, requesting it to block for a specified duration, effectively disrupting most services and leading to a complete denial of service on the AD DC. The DoS affects all other services as "rpcecho" runs in the main RPC task. |
| CVE-2023-4091 | Medium | 2023-11-03 | Not applicable | No public exploit | A vulnerability was discovered in Samba, where the flaw allows SMB clients to truncate files, even with read-only permissions when the Samba VFS module "acl_xattr" is configured with "acl_xattr:ignore system acls = yes". The SMB protocol allows opening files when the client requests read-only access but then implicitly truncates the opened file to 0 bytes if the client specifies a separate OVERWRITE create disposition request. The issue arises in configurations that bypass kernel file system permissions checks, relying solely on Samba's permissions. |
| CVE-2023-3961 | Critical | 2023-11-03 | Not applicable | No public exploit | A path traversal vulnerability was identified in Samba when processing client pipe names connecting to Unix domain sockets within a private directory. Samba typically uses this mechanism to connect SMB clients to remote procedure call (RPC) services like SAMR LSA or SPOOLSS, which Samba initiates on demand. However, due to inadequate sanitization of incoming client pipe names, allowing a client to send a pipe name containing Unix directory traversal characters (../). This could result in SMB clients connecting as root to Unix domain sockets outside the private directory. If an attacker or client managed to send a pipe name resolving to an external service using an existing Unix domain socket, it could potentially lead to unauthorized access to the service and consequential adverse events, including compromise or service crashes. |