Oracle Critical Patch Update April 2024
Released April 2024 · Oracle's advisory ↗ · ← Critical Patch Update, January 2024 · Critical Patch Update, July 2024 →
312 CVEs in this release, one square each
By status
20Protected by Waratek6Mitigation candidate137No exploit published40Outside Waratek scope108Not applicable1Withdrawn CVE
12Exploited, marked by the ring
No exploit published. For 82 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 108 matches · 8 protected · 4 exploited · 2 CISA KEV · 4 public PoC · 3 EPSS ≥ 0.5
Protected by Waratek
8
7.4%
Rule in development
0
0.0%
Mitigation candidate
4
3.7%
No exploit published
96
88.9%
blocked by ARMR today
8
7.4%
partly blocked
0
0.0%
not blocked
100
92.6%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
4
3.7%
Working exploit published
0
0.0%
Proof of concept only
3
2.8%
Forecast only
0
0.0%
No public exploit
101
93.5%
split by
peak 71 / month
Oct 236
Protected by Waratek1
Mitigation candidate1
No exploit published4
Critical2
High3
Medium1
blocked by ARMR today1
not blocked5
Exploited2
No public exploit4
Nov 237
Protected by Waratek1
No exploit published6
Critical1
High4
Medium2
blocked by ARMR today1
not blocked6
No public exploit7
Dec 232
No exploit published2
High1
Medium1
not blocked2
No public exploit2
Jan 245
Protected by Waratek2
No exploit published3
High4
Medium1
blocked by ARMR today2
not blocked3
No public exploit5
Feb 2415
Protected by Waratek2
Mitigation candidate2
No exploit published11
Critical1
High6
Medium7
Low1
blocked by ARMR today2
not blocked13
Exploited2
Proof of concept only2
No public exploit11
Mar 242
Protected by Waratek1
No exploit published1
High2
blocked by ARMR today1
not blocked1
No public exploit2
Apr 2471
Protected by Waratek1
Mitigation candidate1
No exploit published69
Critical2
High15
Medium48
Low6
blocked by ARMR today1
not blocked70
Proof of concept only1
No public exploit70
Oct 23Nov 23Dec 23Jan 24Feb 24Mar 24Apr 24
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-46337 | Critical | 2023-11-20 | No exploit published | No public exploit | A cleverly devised username might bypass LDAP authentication checks. In LDAP-authenticated Derby installations, this could let an attacker fill up the disk by creating junk Derby databases. In LDAP-authenticated Derby installations, this could also allow the attacker to execute malware which was visible to and executable by the account which booted the Derby server. In LDAP-protected databases which weren't also protected by SQL GRANT/REVOKE authorization, this vulnerability could also let an attacker view and corrupt sensitive data and run sensitive database functions and procedures. Mitigation: Users should upgrade to Java 21 and Derby 10.17.1.0. Alternatively, users who wish to remain on older Java versions should build their own Derby distribution from one of the release families to which the fix was backported: 10.16, 10.15, and 10.14. Those are the releases which correspond, respectively, with Java LTS versions 17, 11, and 8. |
| CVE-2023-4043 | High | 2023-11-03 | No exploit published | No public exploit | In Eclipse Parsson before versions 1.1.4 and 1.0.5, Parsing JSON from untrusted sources can lead malicious actors to exploit the fact that the built-in support for parsing numbers with large scale in Java has a number of edge cases where the input text of a number can lead to much larger processing time than one would expect. To mitigate the risk, parsson put in place a size limit for the numbers as well as their scale. |
| CVE-2023-46604 | Critical | 2023-10-27 | Protected by Waratek | Exploited | The Java OpenWire protocol marshaller is vulnerable to Remote Code Execution. This vulnerability may allow a remote attacker with network access to either a Java-based OpenWire broker or client to run arbitrary shell commands by manipulating serialized class types in the OpenWire protocol to cause either the client or the broker (respectively) to instantiate any class on the classpath. Users are recommended to upgrade both brokers and clients to version 5.15.16, 5.16.7, 5.17.6, or 5.18.3 which fixes this issue. |
| CVE-2023-44483 | Medium | 2023-10-20 | No exploit published | No public exploit | All versions of Apache Santuario - XML Security for Java prior to 2.2.6, 2.3.4, and 3.0.3, when using the JSR 105 API, are vulnerable to an issue where a private key may be disclosed in log files when generating an XML Signature and logging with debug level is enabled. Users are recommended to upgrade to version 2.2.6, 2.3.4, or 3.0.3, which fixes this issue. |
| CVE-2023-5072 | High | 2023-10-12 | No exploit published | No public exploit | Denial of Service in JSON-Java versions up to and including 20230618. A bug in the parser means that an input string of modest size can lead to indefinite amounts of memory being used. |
| CVE-2023-44981 | Critical | 2023-10-11 | No exploit published | No public exploit | Authorization Bypass Through User-Controlled Key vulnerability in Apache ZooKeeper. If SASL Quorum Peer authentication is enabled in ZooKeeper (quorum.auth.enableSasl=true), the authorization is done by verifying that the instance part in SASL authentication ID is listed in zoo.cfg server list. The instance part in SASL auth ID is optional and if it's missing, like 'eve@EXAMPLE.COM', the authorization check will be skipped. As a result an arbitrary endpoint could join the cluster and begin propagating counterfeit changes to the leader, essentially giving it complete read-write access to the data tree. Quorum Peer authentication is not enabled by default. Users are recommended to upgrade to version 3.9.1, 3.8.3, 3.7.2, which fixes the issue. Alternately ensure the ensemble election/quorum communication is protected by a firewall as this will mitigate the issue. See the documentation for more details on correct cluster administration. |
| CVE-2023-44487 | High | 2023-10-10 | Mitigation candidate | Exploited | The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023. |
| CVE-2023-36478 | High | 2023-10-10 | No exploit published | No public exploit | Eclipse Jetty provides a web server and servlet container. In versions 11.0.0 through 11.0.15, 10.0.0 through 10.0.15, and 9.0.0 through 9.4.52, an integer overflow in `MetaDataBuilder.checkSize` allows for HTTP/2 HPACK header values to exceed their size limit. `MetaDataBuilder.java` determines if a header name or value exceeds the size limit, and throws an exception if the limit is exceeded. However, when length is very large and huffman is true, the multiplication by 4 in line 295 will overflow, and length will become negative. `(_size+length)` will now be negative, and the check on line 296 will not be triggered. Furthermore, `MetaDataBuilder.checkSize` allows for user-entered HPACK header value sizes to be negative, potentially leading to a very large buffer allocation later on when the user-entered size is multiplied by 2. This means that if a user provides a negative length value (or, more precisely, a length value which, when multiplied by the 4/3 fudge factor, is negative), and this length value is a very large positive number when multiplied by 2, then the user can cause a very large buffer to be allocated on the server. Users of HTTP/2 can be impacted by a remote denial of service attack. The issue has been fixed in versions 11.0.16, 10.0.16, and 9.4.53. There are no known workarounds. |