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
9Exploited, 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 106 matches · 56 in Waratek scope · 8 protected · 2 exploited · 1 CISA KEV · 4 public PoC · 2 EPSS ≥ 0.5
106matches
56in Waratek scope52.8%
8protected7.5%
2exploited1.9%
1CISA KEV0.9%
4public PoC3.8%
2EPSS ≥ 0.51.9%
Protected by Waratek
8
7.5%
Rule in development
0
0.0%
Mitigation candidate
2
1.9%
No exploit published
46
43.4%
Outside Waratek scope
2
1.9%
Not applicable
47
44.3%
Withdrawn CVE
1
0.9%
blocked by ARMR today
8
7.5%
partly blocked
0
0.0%
not blocked
98
92.5%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
2
1.9%
Working exploit published
0
0.0%
Proof of concept only
7
6.6%
Forecast only
0
0.0%
No public exploit
97
91.5%
split by
peak 74 / month
Sep 2211
Protected by Waratek1
Mitigation candidate1
No exploit published3
Outside Waratek scope1
Not applicable4
Withdrawn CVE1
Critical1
High6
Medium3
Unknown1
blocked by ARMR today1
not blocked10
Proof of concept only2
No public exploit9
Oct 2210
Protected by Waratek1
Mitigation candidate1
No exploit published4
Not applicable4
Critical5
High5
blocked by ARMR today1
not blocked9
Exploited1
Proof of concept only2
No public exploit7
Nov 224
Protected by Waratek2
No exploit published1
Not applicable1
Critical2
High2
blocked by ARMR today2
not blocked2
Proof of concept only1
No public exploit3
Dec 227
No exploit published4
Not applicable3
Critical1
High5
Medium1
not blocked7
Proof of concept only2
No public exploit5
Jan 2374
Protected by Waratek4
No exploit published34
Outside Waratek scope1
Not applicable35
Critical1
High24
Medium44
Low5
blocked by ARMR today4
not blocked70
Exploited1
No public exploit73
Sep 22Oct 22Nov 22Dec 22Jan 23
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-40150 | High | 2022-09-16 | No exploit published | No public exploit | Those using Jettison to parse untrusted XML or JSON data may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by Out of memory. This effect may support a denial of service attack. |
| CVE-2022-40149 | High | 2022-09-16 | No exploit published | No public exploit | Those using Jettison to parse untrusted XML or JSON data may be vulnerable to Denial of Service attacks (DOS). 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-2526 | Critical | 2022-09-09 | Outside Waratek scope | No public exploit | A use-after-free vulnerability was found in systemd. This issue occurs due to the on_stream_io() function and dns_stream_complete() function in 'resolved-dns-stream.c' not incrementing the reference counting for the DnsStream object. Therefore, other functions and callbacks called can dereference the DNSStream object, causing the use-after-free when the reference is still used later. |
| CVE-2020-10735 | High | 2022-09-09 | Not applicable | No public exploit | A flaw was found in python. In algorithms with quadratic time complexity using non-binary bases, when using int("text"), a system could take 50ms to parse an int string with 100,000 digits and 5s for 1,000,000 digits (float, decimal, int.from_bytes(), and int() for binary bases 2, 4, 8, 16, and 32 are not affected). The highest threat from this vulnerability is to system availability. |
| CVE-2022-38752 | Medium | 2022-09-05 | Protected by Waratek | Proof of concept only | Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stack-overflow. |
| CVE-2022-36055 | Medium | 2022-09-01 | Not applicable | No public exploit | Helm is a tool for managing Charts. Charts are packages of pre-configured Kubernetes resources. Fuzz testing, provided by the CNCF, identified input to functions in the _strvals_ package that can cause an out of memory panic. The _strvals_ package contains a parser that turns strings in to Go structures. The _strvals_ package converts these strings into structures Go can work with. Some string inputs can cause array data structures to be created causing an out of memory panic. Applications that use the _strvals_ package in the Helm SDK to parse user supplied input can suffer a Denial of Service when that input causes a panic that cannot be recovered from. The Helm Client will panic with input to `--set`, `--set-string`, and other value setting flags that causes an out of memory panic. Helm is not a long running service so the panic will not affect future uses of the Helm client. This issue has been resolved in 3.9.4. SDK users can validate strings supplied by users won't create large arrays causing significant memory usage before passing them to the _strvals_ functions. |