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 201 matches · 87 in Waratek scope · 7 protected · 9 exploited · 1 CISA KEV · 15 public PoC · 9 EPSS ≥ 0.5
201matches
87in Waratek scope43.3%
7protected3.5%
9exploited4.5%
1CISA KEV0.5%
15public PoC7.5%
9EPSS ≥ 0.54.5%
Protected by Waratek
7
3.5%
Rule in development
0
0.0%
Mitigation candidate
2
1.0%
No exploit published
78
38.8%
Outside Waratek scope
3
1.5%
Not applicable
111
55.2%
Withdrawn CVE
0
0.0%
blocked by ARMR today
7
3.5%
partly blocked
0
0.0%
not blocked
194
96.5%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 84 / month
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. |