Oracle Critical Patch Update April 2023
Released April 2023 · Oracle's advisory ↗ · ← Critical Patch Update, January 2023 · Critical Patch Update, July 2023 →
328 CVEs in this release, one square each
By status
47Protected by Waratek10Mitigation candidate123No exploit published3Outside Waratek scope145Not applicable
12Exploited, marked by the ring
No exploit published. For 55 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 207 matches · 98 in Waratek scope · 17 protected · 7 exploited · 0 CISA KEV · 15 public PoC · 12 EPSS ≥ 0.5
207matches
98in Waratek scope47.3%
17protected8.2%
7exploited3.4%
0CISA KEV0.0%
15public PoC7.2%
12EPSS ≥ 0.55.8%
Protected by Waratek
17
8.2%
Rule in development
0
0.0%
Mitigation candidate
5
2.4%
No exploit published
76
36.7%
Outside Waratek scope
3
1.4%
Not applicable
106
51.2%
Withdrawn CVE
0
0.0%
blocked by ARMR today
17
8.2%
partly blocked
0
0.0%
not blocked
189
91.3%
not established
1
0.5%
unrecorded
0
0.0%
Exploited
7
3.4%
Working exploit published
0
0.0%
Proof of concept only
35
16.9%
Forecast only
4
1.9%
No public exploit
161
77.8%
split by
peak 91 / quarter
Q3 2236
Protected by Waratek4
Mitigation candidate2
No exploit published12
Outside Waratek scope1
Not applicable17
Critical11
High14
Medium10
Low1
blocked by ARMR today4
not blocked32
Proof of concept only12
Forecast only1
No public exploit23
Q4 2249
Protected by Waratek6
Mitigation candidate2
No exploit published15
Outside Waratek scope2
Not applicable24
Critical11
High34
Medium4
blocked by ARMR today6
not blocked43
Exploited4
Proof of concept only13
No public exploit32
Q1 2328
Protected by Waratek1
No exploit published6
Not applicable21
Critical4
High13
Medium10
Low1
blocked by ARMR today1
not blocked27
Exploited2
Proof of concept only9
Forecast only2
No public exploit15
Q2 2391
Protected by Waratek6
Mitigation candidate1
No exploit published43
Not applicable41
High14
Medium68
Low9
blocked by ARMR today6
not blocked84
not established1
Exploited1
Proof of concept only1
Forecast only1
No public exploit88
Q3 230
Q4 230
Q1 242
Not applicable2
Critical2
not blocked2
No public exploit2
Q2 241
Not applicable1
Medium1
not blocked1
No public exploit1
Q3 22Q4 22Q1 23Q2 23Q3 23Q4 23Q1 24Q2 24
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-2191 | High | 2022-07-07 | No exploit published | No public exploit | In Eclipse Jetty versions 10.0.0 thru 10.0.9, and 11.0.0 thru 11.0.9 versions, SslConnection does not release ByteBuffers from configured ByteBufferPool in case of error code paths. |
| CVE-2022-2048 | High | 2022-07-07 | No exploit published | No public exploit | In Eclipse Jetty HTTP/2 server implementation, when encountering an invalid HTTP/2 request, the error handling has a bug that can wind up not properly cleaning up the active connections and associated resources. This can lead to a Denial of Service scenario where there are no enough resources left to process good requests. |
| CVE-2022-2047 | Low | 2022-07-07 | No exploit published | No public exploit | In Eclipse Jetty versions 9.4.0 thru 9.4.46, and 10.0.0 thru 10.0.9, and 11.0.0 thru 11.0.9 versions, the parsing of the authority segment of an http scheme URI, the Jetty HttpURI class improperly detects an invalid input as a hostname. This can lead to failures in a Proxy scenario. |
| CVE-2022-33980 | Critical | 2022-07-06 | Mitigation candidate | Proof of concept only | Apache Commons Configuration performs variable interpolation, allowing properties to be dynamically evaluated and expanded. The standard format for interpolation is "${prefix:name}", where "prefix" is used to locate an instance of org.apache.commons.configuration2.interpol.Lookup that performs the interpolation. Starting with version 2.4 and continuing through 2.7, the set of default Lookup instances included interpolators that could result in arbitrary code execution or contact with remote servers. These lookups are: - "script" - execute expressions using the JVM script execution engine (javax.script) - "dns" - resolve dns records - "url" - load values from urls, including from remote servers Applications using the interpolation defaults in the affected versions may be vulnerable to remote code execution or unintentional contact with remote servers if untrusted configuration values are used. Users are recommended to upgrade to Apache Commons Configuration 2.8.0, which disables the problematic interpolators by default. |
| 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-2022-2097 | Medium | 2022-07-05 | Not applicable | No public exploit | AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimised implementation will not encrypt the entirety of the data under some circumstances. This could reveal sixteen bytes of data that was preexisting in the memory that wasn't written. In the special case of "in place" encryption, sixteen bytes of the plaintext would be revealed. Since OpenSSL does not support OCB based cipher suites for TLS and DTLS, they are both unaffected. Fixed in OpenSSL 3.0.5 (Affected 3.0.0-3.0.4). Fixed in OpenSSL 1.1.1q (Affected 1.1.1-1.1.1p). |
| CVE-2022-2274 | Critical | 2022-07-01 | Not applicable | Proof of concept only | The OpenSSL 3.0.4 release introduced a serious bug in the RSA implementation for X86_64 CPUs supporting the AVX512IFMA instructions. This issue makes the RSA implementation with 2048 bit private keys incorrect on such machines and memory corruption will happen during the computation. As a consequence of the memory corruption an attacker may be able to trigger a remote code execution on the machine performing the computation. SSL/TLS servers or other servers using 2048 bit RSA private keys running on machines supporting AVX512IFMA instructions of the X86_64 architecture are affected by this issue. |