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
21Protected by Waratek7Mitigation candidate138No exploit published14Outside Waratek scope131Not 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 101 matches · 0 protected · 3 exploited · 1 CISA KEV · 4 public PoC · 2 EPSS ≥ 0.5
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
5
5.0%
No exploit published
96
95.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
101
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
3
3.0%
Working exploit published
0
0.0%
Proof of concept only
4
4.0%
Forecast only
0
0.0%
No public exploit
94
93.1%
split by
peak 70 / month
Oct 235
Mitigation candidate1
No exploit published4
Critical1
High3
Medium1
not blocked5
Exploited1
No public exploit4
Nov 236
No exploit published6
Critical1
High3
Medium2
not blocked6
No public exploit6
Dec 232
No exploit published2
High1
Medium1
not blocked2
No public exploit2
Jan 243
No exploit published3
High3
not blocked3
No public exploit3
Feb 2414
Mitigation candidate3
No exploit published11
Critical1
High7
Medium5
Low1
not blocked14
Exploited2
Proof of concept only3
No public exploit9
Mar 241
No exploit published1
High1
not blocked1
No public exploit1
Apr 2470
Mitigation candidate1
No exploit published69
Critical2
High15
Medium48
Low5
not blocked70
Proof of concept only1
No public exploit69
Oct 23Nov 23Dec 23Jan 24Feb 24Mar 24Apr 24
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| 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. |