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
10Exploited, 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 11 matches · 5 in Waratek scope · 3 protected · 2 exploited · 0 CISA KEV · 3 public PoC · 2 EPSS ≥ 0.5
11matches
5in Waratek scope45.5%
3protected27.3%
2exploited18.2%
0CISA KEV0.0%
3public PoC27.3%
2EPSS ≥ 0.518.2%
Protected by Waratek
3
27.3%
Rule in development
0
0.0%
Mitigation candidate
1
9.1%
No exploit published
1
9.1%
Outside Waratek scope
0
0.0%
Not applicable
6
54.5%
Withdrawn CVE
0
0.0%
blocked by ARMR today
3
27.3%
partly blocked
0
0.0%
not blocked
8
72.7%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
2
18.2%
Working exploit published
0
0.0%
Proof of concept only
3
27.3%
Forecast only
0
0.0%
No public exploit
6
54.5%
split by
peak 3 / month
Nov 222
Protected by Waratek2
Critical2
blocked by ARMR today2
Proof of concept only1
No public exploit1
Dec 223
Protected by Waratek1
Mitigation candidate1
Not applicable1
Critical3
blocked by ARMR today1
not blocked2
Exploited1
Proof of concept only1
No public exploit1
Jan 231
Not applicable1
Critical1
not blocked1
No public exploit1
Feb 232
No exploit published1
Not applicable1
Critical2
not blocked2
Proof of concept only1
No public exploit1
Mar 231
Not applicable1
Critical1
not blocked1
Exploited1
Apr 230
May 230
Jun 230
Jul 230
Aug 230
Sep 230
Oct 230
Nov 230
Dec 230
Jan 240
Feb 242
Not applicable2
Critical2
not blocked2
No public exploit2
Dec 22Feb 23Apr 23Jun 23Aug 23Oct 23Dec 23Feb 24
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2021-21575 | Critical | 2024-02-02 | Not applicable | No public exploit | Dell BSAFE Micro Edition Suite, versions before 4.5.2, contain an Observable Timing Discrepancy Vulnerability. |
| CVE-2020-29504 | Critical | 2024-02-02 | Not applicable | No public exploit | Dell BSAFE Crypto-C Micro Edition, versions before 4.1.5, and Dell BSAFE Micro Edition Suite, versions before 4.5.2, contain a Missing Required Cryptographic Step Vulnerability. |
| CVE-2023-25690 | Critical | 2023-03-07 | Not applicable | Exploited | Some mod_proxy configurations on Apache HTTP Server versions 2.4.0 through 2.4.55 allow a HTTP Request Smuggling attack. Configurations are affected when mod_proxy is enabled along with some form of RewriteRule or ProxyPassMatch in which a non-specific pattern matches some portion of the user-supplied request-target (URL) data and is then re-inserted into the proxied request-target using variable substitution. For example, something like: RewriteEngine on RewriteRule "^/here/(.*)" "http://example.com:8080/elsewhere?$1"; [P] ProxyPassReverse /here/ http://example.com:8080/ Request splitting/smuggling could result in bypass of access controls in the proxy server, proxying unintended URLs to existing origin servers, and cache poisoning. Users are recommended to update to at least version 2.4.56 of Apache HTTP Server. |
| CVE-2023-23914 | Critical | 2023-02-23 | Not applicable | Proof of concept only | A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functionality fail when multiple URLs are requested serially. Using its HSTS support, curl can be instructed to use HTTPS instead of usingan insecure clear-text HTTP step even when HTTP is provided in the URL. ThisHSTS mechanism would however surprisingly be ignored by subsequent transferswhen done on the same command line because the state would not be properlycarried on. |
| CVE-2023-25613 | Critical | 2023-02-20 | No exploit published | No public exploit | An LDAP Injection vulnerability exists in the LdapIdentityBackend of Apache Kerby before 2.0.3. |
| CVE-2022-36760 | Critical | 2023-01-17 | Not applicable | No public exploit | Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling') vulnerability in mod_proxy_ajp of Apache HTTP Server allows an attacker to smuggle requests to the AJP server it forwards requests to. This issue affects Apache HTTP Server Apache HTTP Server 2.4 version 2.4.54 and prior versions. |
| CVE-2022-47629 | Critical | 2022-12-20 | Not applicable | No public exploit | Libksba before 1.6.3 is prone to an integer overflow vulnerability in the CRL signature parser. |
| CVE-2022-46364 | Critical | 2022-12-13 | Mitigation candidate | Proof of concept only | A SSRF vulnerability in parsing the href attribute of XOP:Include in MTOM requests in versions of Apache CXF before 3.5.5 and 3.4.10 allows an attacker to perform SSRF style attacks on webservices that take at least one parameter of any type. |
| CVE-2022-1471 | Critical | 2022-12-01 | Protected by Waratek | Exploited | SnakeYaml's Constructor() class does not restrict types which can be instantiated during deserialization. Deserializing yaml content provided by an attacker can lead to remote code execution. We recommend using SnakeYaml's SafeConsturctor when parsing untrusted content to restrict deserialization. We recommend upgrading to version 2.0 and beyond. |
| CVE-2022-45047 | Critical | 2022-11-16 | Protected by Waratek | Proof of concept only | Class org.apache.sshd.server.keyprovider.SimpleGeneratorHostKeyProvider in Apache MINA SSHD <= 2.9.1 uses Java deserialization to load a serialized java.security.PrivateKey. The class is one of several implementations that an implementor using Apache MINA SSHD can choose for loading the host keys of an SSH server. |
| CVE-2022-37865 | Critical | 2022-11-07 | Protected by Waratek | No public exploit | With Apache Ivy 2.4.0 an optional packaging attribute has been introduced that allows artifacts to be unpacked on the fly if they used pack200 or zip packaging. For artifacts using the "zip", "jar" or "war" packaging Ivy prior to 2.5.1 doesn't verify the target path when extracting the archive. An archive containing absolute paths or paths that try to traverse "upwards" using ".." sequences can then write files to any location on the local fie system that the user executing Ivy has write access to. Ivy users of version 2.4.0 to 2.5.0 should upgrade to Ivy 2.5.1. |