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 102 matches · 7 protected · 2 exploited · 0 CISA KEV · 2 public PoC · 1 EPSS ≥ 0.5
Protected by Waratek
7
6.9%
Rule in development
0
0.0%
Mitigation candidate
3
2.9%
No exploit published
92
90.2%
blocked by ARMR today
7
6.9%
partly blocked
0
0.0%
not blocked
95
93.1%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
2
2.0%
Working exploit published
0
0.0%
Proof of concept only
3
2.9%
Forecast only
0
0.0%
No public exploit
97
95.1%
split by
peak 71 / month
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
Nov 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. |