Oracle Critical Patch Update October 2023
Released October 2023 · Oracle's advisory ↗ · ← Critical Patch Update, July 2023 · Critical Patch Update, January 2024 →
245 CVEs in this release, one square each
By status
16Protected by Waratek7Mitigation candidate91No exploit published6Outside Waratek scope125Not applicable
8Exploited, marked by the ring
No exploit published. For 35 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 209 matches · 87 in Waratek scope · 10 protected · 5 exploited · 0 CISA KEV · 12 public PoC · 8 EPSS ≥ 0.5
209matches
87in Waratek scope41.6%
10protected4.8%
5exploited2.4%
0CISA KEV0.0%
12public PoC5.7%
8EPSS ≥ 0.53.8%
Protected by Waratek
10
4.8%
Rule in development
0
0.0%
Mitigation candidate
3
1.4%
No exploit published
74
35.4%
Outside Waratek scope
5
2.4%
Not applicable
117
56.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
10
4.8%
partly blocked
0
0.0%
not blocked
198
94.7%
not established
1
0.5%
unrecorded
0
0.0%
Exploited
5
2.4%
Working exploit published
0
0.0%
Proof of concept only
46
22.0%
Forecast only
3
1.4%
No public exploit
155
74.2%
split by
peak 75 / month
Jun 228
Protected by Waratek1
No exploit published1
Not applicable6
Critical1
High5
Medium2
blocked by ARMR today1
not blocked7
Proof of concept only3
No public exploit5
Jul 223
Mitigation candidate1
Outside Waratek scope1
Not applicable1
Critical1
High1
Medium1
not blocked3
Proof of concept only3
Aug 222
Protected by Waratek2
Critical1
Medium1
blocked by ARMR today2
Proof of concept only1
No public exploit1
Sep 223
Protected by Waratek1
No exploit published2
Critical1
High2
blocked by ARMR today1
not blocked2
Proof of concept only3
Oct 226
Protected by Waratek1
No exploit published2
Not applicable3
Critical1
High5
blocked by ARMR today1
not blocked5
Proof of concept only1
No public exploit5
Nov 224
Protected by Waratek1
No exploit published1
Not applicable2
Critical1
High2
Low1
blocked by ARMR today1
not blocked3
Proof of concept only1
No public exploit3
Dec 2211
Protected by Waratek1
No exploit published6
Outside Waratek scope1
Not applicable3
Critical1
High7
Medium3
blocked by ARMR today1
not blocked10
Exploited1
Proof of concept only6
No public exploit4
Jan 234
Not applicable4
High1
Medium3
not blocked4
Forecast only1
No public exploit3
Feb 239
No exploit published2
Not applicable7
Critical1
High5
Medium3
not blocked9
Proof of concept only4
No public exploit5
Mar 2316
No exploit published5
Not applicable11
Critical2
High9
Medium5
not blocked16
Exploited1
Proof of concept only5
No public exploit10
Apr 2311
Protected by Waratek1
No exploit published6
Not applicable4
Critical2
High2
Medium7
blocked by ARMR today1
not blocked10
No public exploit11
May 2310
No exploit published2
Not applicable8
High4
Medium6
not blocked10
Proof of concept only5
Forecast only1
No public exploit4
Jun 2310
No exploit published6
Not applicable4
High7
Medium3
not blocked10
Proof of concept only2
No public exploit8
Jul 2323
Protected by Waratek1
No exploit published5
Outside Waratek scope1
Not applicable16
Critical4
High10
Medium9
blocked by ARMR today1
not blocked22
Exploited1
Proof of concept only7
Forecast only1
No public exploit14
Aug 236
Mitigation candidate1
No exploit published2
Not applicable3
Critical1
High2
Medium3
not blocked6
Exploited1
Proof of concept only1
No public exploit4
Sep 235
No exploit published3
Not applicable2
High1
Medium3
Low1
not blocked5
Proof of concept only2
No public exploit3
Oct 2375
Protected by Waratek1
Mitigation candidate1
No exploit published31
Outside Waratek scope2
Not applicable40
Critical4
High11
Medium54
Low6
blocked by ARMR today1
not blocked73
not established1
Exploited1
Proof of concept only2
No public exploit72
Nov 233
Not applicable3
High2
Medium1
not blocked3
No public exploit3
Jul 22Sep 22Nov 22Jan 23Mar 23May 23Jul 23Sep 23Nov 23
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-31129 | High | 2022-07-06 | Not applicable | Proof of concept only | moment is a JavaScript date library for parsing, validating, manipulating, and formatting dates. Affected versions of moment were found to use an inefficient parsing algorithm. Specifically using string-to-date parsing in moment (more specifically rfc2822 parsing, which is tried by default) has quadratic (N^2) complexity on specific inputs. Users may notice a noticeable slowdown is observed with inputs above 10k characters. Users who pass user-provided strings without sanity length checks to moment constructor are vulnerable to (Re)DoS attacks. The problem is patched in 2.29.4, the patch can be applied to all affected versions with minimal tweaking. Users are advised to upgrade. Users unable to upgrade should consider limiting date lengths accepted from user input. |
| CVE-2021-33036 | High | 2022-06-15 | Protected by Waratek | No public exploit | In Apache Hadoop 2.2.0 to 2.10.1, 3.0.0-alpha1 to 3.1.4, 3.2.0 to 3.2.2, and 3.3.0 to 3.3.1, a user who can escalate to yarn user can possibly run arbitrary commands as root user. Users should upgrade to Apache Hadoop 2.10.2, 3.2.3, 3.3.2 or higher. |
| CVE-2021-37404 | Critical | 2022-06-13 | No exploit published | No public exploit | There is a potential heap buffer overflow in Apache Hadoop libhdfs native code. Opening a file path provided by user without validation may result in a denial of service or arbitrary code execution. Users should upgrade to Apache Hadoop 2.10.2, 3.2.3, 3.3.2 or higher. |
| CVE-2022-30115 | Medium | 2022-06-02 | Not applicable | No public exploit | Using its HSTS support, curl can be instructed to use HTTPS directly insteadof using an insecure clear-text HTTP step even when HTTP is provided in theURL. This mechanism could be bypassed if the host name in the given URL used atrailing dot while not using one when it built the HSTS cache. Or the otherway around - by having the trailing dot in the HSTS cache and *not* using thetrailing dot in the URL. |
| CVE-2022-27782 | High | 2022-06-02 | Not applicable | Proof of concept only | libcurl would reuse a previously created connection even when a TLS or SSHrelated option had been changed that should have prohibited reuse.libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse if one of them matches the setup. However, several TLS andSSH settings were left out from the configuration match checks, making themmatch too easily. |
| CVE-2022-27781 | High | 2022-06-02 | Not applicable | Proof of concept only | libcurl provides the `CURLOPT_CERTINFO` option to allow applications torequest details to be returned about a server's certificate chain.Due to an erroneous function, a malicious server could make libcurl built withNSS get stuck in a never-ending busy-loop when trying to retrieve thatinformation. |
| CVE-2022-27780 | High | 2022-06-02 | Not applicable | Proof of concept only | The curl URL parser wrongly accepts percent-encoded URL separators like '/'when decoding the host name part of a URL, making it a *different* URL usingthe wrong host name when it is later retrieved.For example, a URL like `http://example.com%2F127.0.0.1/`, would be allowed bythe parser and get transposed into `http://example.com/127.0.0.1/`. This flawcan be used to circumvent filters, checks and more. |
| CVE-2022-27779 | Medium | 2022-06-02 | Not applicable | No public exploit | libcurl wrongly allows cookies to be set for Top Level Domains (TLDs) if thehost name is provided with a trailing dot.curl can be told to receive and send cookies. curl's "cookie engine" can bebuilt with or without [Public Suffix List](https://publicsuffix.org/)awareness. If PSL support not provided, a more rudimentary check exists to atleast prevent cookies from being set on TLDs. This check was broken if thehost name in the URL uses a trailing dot.This can allow arbitrary sites to set cookies that then would get sent to adifferent and unrelated site or domain. |
| CVE-2022-27778 | High | 2022-06-02 | Not applicable | No public exploit | A use of incorrectly resolved name vulnerability fixed in 7.83.1 might remove the wrong file when `--no-clobber` is used together with `--remove-on-error`. |