Oracle Critical Patch Update January 2024
Released January 2024 · Oracle's advisory ↗ · ← Critical Patch Update, October 2023 · Critical Patch Update, April 2024 →
236 CVEs in this release, one square each
By status
27Protected by Waratek5Mitigation candidate104No exploit published9Outside Waratek scope91Not applicable
9Exploited, 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 205 matches · 111 in Waratek scope · 16 protected · 7 exploited · 4 CISA KEV · 13 public PoC · 13 EPSS ≥ 0.5
205matches
111in Waratek scope54.1%
16protected7.8%
7exploited3.4%
4CISA KEV2.0%
13public PoC6.3%
13EPSS ≥ 0.56.3%
Protected by Waratek
16
7.8%
Rule in development
0
0.0%
Mitigation candidate
4
2.0%
No exploit published
91
44.4%
Outside Waratek scope
7
3.4%
Not applicable
87
42.4%
Withdrawn CVE
0
0.0%
blocked by ARMR today
16
7.8%
partly blocked
0
0.0%
not blocked
189
92.2%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 86 / quarter
Q3 224
Protected by Waratek2
No exploit published1
Not applicable1
Critical2
High1
Medium1
blocked by ARMR today2
not blocked2
Proof of concept only4
Q4 2216
Protected by Waratek3
Mitigation candidate1
No exploit published7
Not applicable5
Critical4
High11
Medium1
blocked by ARMR today3
not blocked13
Exploited1
Proof of concept only5
No public exploit10
Q1 2314
Protected by Waratek1
No exploit published3
Not applicable10
High6
Medium8
blocked by ARMR today1
not blocked13
Exploited1
Proof of concept only3
No public exploit10
Q2 2320
No exploit published10
Not applicable10
Critical1
High14
Medium5
not blocked20
Proof of concept only6
Forecast only1
No public exploit13
Q3 2338
Protected by Waratek3
No exploit published18
Outside Waratek scope2
Not applicable15
Critical3
High17
Medium15
Low3
blocked by ARMR today3
not blocked35
Proof of concept only3
No public exploit35
Q4 2327
Protected by Waratek3
Mitigation candidate3
No exploit published11
Not applicable10
Critical5
High12
Medium7
Low3
blocked by ARMR today3
not blocked24
Exploited4
Working exploit published1
Proof of concept only3
No public exploit19
Q1 2486
Protected by Waratek4
No exploit published41
Outside Waratek scope5
Not applicable36
High12
Medium63
Low11
blocked by ARMR today4
not blocked82
Exploited1
Proof of concept only1
No public exploit84
Q3 22Q4 22Q1 23Q2 23Q3 23Q4 23Q1 24
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-42003 | High | 2022-10-02 | No exploit published | No public exploit | In FasterXML jackson-databind before versions 2.13.4.1 and 2.12.17.1, resource exhaustion can occur because of a lack of a check in primitive value deserializers to avoid deep wrapper array nesting, when the UNWRAP_SINGLE_VALUE_ARRAYS feature is enabled. |
| CVE-2022-36944 | Critical | 2022-09-23 | Protected by Waratek | Proof of concept only | Scala 2.13.x before 2.13.9 has a Java deserialization chain in its JAR file. On its own, it cannot be exploited. There is only a risk in conjunction with Java object deserialization within an application. In such situations, it allows attackers to erase contents of arbitrary files, make network connections, or possibly run arbitrary code (specifically, Function0 functions) via a gadget chain. |
| CVE-2022-40152 | High | 2022-09-16 | No exploit published | Proof of concept only | Those using Woodstox to parse XML data may be vulnerable to Denial of Service attacks (DOS) if DTD support is enabled. If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow. This effect may support a denial of service attack. |
| CVE-2022-36033 | Medium | 2022-08-29 | Protected by Waratek | Proof of concept only | jsoup is a Java HTML parser, built for HTML editing, cleaning, scraping, and cross-site scripting (XSS) safety. jsoup may incorrectly sanitize HTML including `javascript:` URL expressions, which could allow XSS attacks when a reader subsequently clicks that link. If the non-default `SafeList.preserveRelativeLinks` option is enabled, HTML including `javascript:` URLs that have been crafted with control characters will not be sanitized. If the site that this HTML is published on does not set a Content Security Policy, an XSS attack is then possible. This issue is patched in jsoup 1.15.3. Users should upgrade to this version. Additionally, as the unsanitized input may have been persisted, old content should be cleaned again using the updated version. To remediate this issue without immediately upgrading: - disable `SafeList.preserveRelativeLinks`, which will rewrite input URLs as absolute URLs - ensure an appropriate [Content Security Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) is defined. (This should be used regardless of upgrading, as a defence-in-depth best practice.) |
| CVE-2022-37434 | Critical | 2022-08-05 | Not applicable | Proof of concept only | zlib through 1.2.12 has a heap-based buffer over-read or buffer overflow in inflate in inflate.c via a large gzip header extra field. NOTE: only applications that call inflateGetHeader are affected. Some common applications bundle the affected zlib source code but may be unable to call inflateGetHeader (e.g., see the nodejs/node reference). |