Oracle Critical Patch Update January 2023
Released January 2023 · Oracle's advisory ↗ · ← Critical Patch Update, October 2022 · Critical Patch Update, April 2023 →
183 CVEs in this release, one square each
By status
29Protected by Waratek5Mitigation candidate66No exploit published3Outside Waratek scope79Not applicable1Withdrawn CVE
10Exploited, marked by the ring
No exploit published. For 40 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 102 matches · 58 in Waratek scope · 25 protected · 9 exploited · 3 CISA KEV · 17 public PoC · 11 EPSS ≥ 0.5
102matches
58in Waratek scope56.9%
25protected24.5%
9exploited8.8%
3CISA KEV2.9%
17public PoC16.7%
11EPSS ≥ 0.510.8%
Protected by Waratek
25
24.5%
Rule in development
0
0.0%
Mitigation candidate
5
4.9%
No exploit published
28
27.5%
Outside Waratek scope
2
2.0%
Not applicable
41
40.2%
Withdrawn CVE
1
1.0%
blocked by ARMR today
25
24.5%
partly blocked
0
0.0%
not blocked
77
75.5%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
9
8.8%
Working exploit published
0
0.0%
Proof of concept only
24
23.5%
Forecast only
0
0.0%
No public exploit
69
67.6%
split by
peak 27 / quarter
Q1 181
Protected by Waratek1
Critical1
blocked by ARMR today1
No public exploit1
Q2 181
Protected by Waratek1
Critical1
blocked by ARMR today1
Exploited1
Q3 180
Q4 180
Q1 191
Not applicable1
Medium1
not blocked1
No public exploit1
Q2 190
Q3 190
Q4 192
Protected by Waratek2
Critical1
Medium1
blocked by ARMR today2
Proof of concept only1
No public exploit1
Q1 200
Q2 202
Protected by Waratek1
No exploit published1
Critical1
Medium1
blocked by ARMR today1
not blocked1
No public exploit2
Q3 200
Q4 202
No exploit published2
High1
Medium1
not blocked2
No public exploit2
Q1 214
No exploit published2
Not applicable2
Critical1
High3
not blocked4
Proof of concept only1
No public exploit3
Q2 212
Protected by Waratek1
No exploit published1
Medium2
blocked by ARMR today1
not blocked1
No public exploit2
Q3 215
No exploit published2
Not applicable3
High4
Medium1
not blocked5
No public exploit5
Q4 217
Protected by Waratek2
Mitigation candidate1
No exploit published1
Not applicable3
Critical1
High2
Medium4
blocked by ARMR today2
not blocked5
Exploited2
Proof of concept only1
No public exploit4
Q1 2215
Protected by Waratek3
No exploit published3
Not applicable9
Critical5
High6
Medium4
blocked by ARMR today3
not blocked12
Exploited1
Proof of concept only5
No public exploit9
Q2 2219
Protected by Waratek7
Mitigation candidate1
No exploit published4
Outside Waratek scope1
Not applicable6
Critical7
High6
Medium6
blocked by ARMR today7
not blocked12
Exploited3
Proof of concept only4
No public exploit12
Q3 2227
Protected by Waratek4
Mitigation candidate2
No exploit published7
Outside Waratek scope1
Not applicable12
Withdrawn CVE1
Critical4
High18
Medium4
Unknown1
blocked by ARMR today4
not blocked23
Proof of concept only9
No public exploit18
Q4 2214
Protected by Waratek3
Mitigation candidate1
No exploit published5
Not applicable5
Critical7
High7
blocked by ARMR today3
not blocked11
Exploited2
Proof of concept only3
No public exploit9
Q2 18Q4 18Q2 19Q4 19Q2 20Q4 20Q2 21Q4 21Q2 22Q4 22
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2018-1273 | Critical | 2018-04-11 | Protected by Waratek | Exploited | Spring Data Commons, versions prior to 1.13 to 1.13.10, 2.0 to 2.0.5, and older unsupported versions, contain a property binder vulnerability caused by improper neutralization of special elements. An unauthenticated remote malicious user (or attacker) can supply specially crafted request parameters against Spring Data REST backed HTTP resources or using Spring Data's projection-based request payload binding hat can lead to a remote code execution attack. |
| CVE-2018-7489 | Critical | 2018-02-26 | Protected by Waratek | No public exploit | FasterXML jackson-databind before 2.7.9.3, 2.8.x before 2.8.11.1 and 2.9.x before 2.9.5 allows unauthenticated remote code execution because of an incomplete fix for the CVE-2017-7525 deserialization flaw. This is exploitable by sending maliciously crafted JSON input to the readValue method of the ObjectMapper, bypassing a blacklist that is ineffective if the c3p0 libraries are available in the classpath. |