Oracle Critical Patch Update July 2024
Released July 2024 · Oracle's advisory ↗ · ← Critical Patch Update, April 2024 · Critical Patch Update, October 2024 →
231 CVEs in this release, one square each
By status
16Protected by Waratek6Mitigation candidate99No exploit published6Outside Waratek scope104Not applicable
9Exploited, marked by the ring
No exploit published. For 34 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 205 matches · 99 in Waratek scope · 8 protected · 8 exploited · 3 CISA KEV · 17 public PoC · 11 EPSS ≥ 0.5
205matches
99in Waratek scope48.3%
8protected3.9%
8exploited3.9%
3CISA KEV1.5%
17public PoC8.3%
11EPSS ≥ 0.55.4%
Protected by Waratek
8
3.9%
Rule in development
0
0.0%
Mitigation candidate
5
2.4%
No exploit published
86
42.0%
Outside Waratek scope
4
2.0%
Not applicable
102
49.8%
Withdrawn CVE
0
0.0%
blocked by ARMR today
8
3.9%
partly blocked
0
0.0%
not blocked
197
96.1%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 63 / quarter
Q3 2210
Protected by Waratek2
Mitigation candidate1
No exploit published5
Not applicable2
Critical3
High4
Medium3
blocked by ARMR today2
not blocked8
Proof of concept only6
No public exploit4
Q4 2210
No exploit published9
Not applicable1
Critical1
High7
Medium2
not blocked10
Proof of concept only4
No public exploit6
Q1 237
No exploit published4
Not applicable3
High3
Medium4
not blocked7
Proof of concept only3
No public exploit4
Q2 232
No exploit published2
High1
Medium1
not blocked2
No public exploit2
Q3 2314
Protected by Waratek1
No exploit published7
Outside Waratek scope1
Not applicable5
Critical3
High2
Medium8
Low1
blocked by ARMR today1
not blocked13
No public exploit14
Q4 2330
Mitigation candidate1
No exploit published9
Outside Waratek scope1
Not applicable19
Critical3
High14
Medium13
not blocked30
Exploited3
Proof of concept only7
No public exploit20
Q1 2446
Protected by Waratek2
Mitigation candidate2
No exploit published17
Not applicable25
Critical4
High19
Medium23
blocked by ARMR today2
not blocked44
Exploited1
Proof of concept only8
Forecast only1
No public exploit36
Q2 2421
Protected by Waratek1
Mitigation candidate1
No exploit published6
Not applicable13
High13
Medium7
Low1
blocked by ARMR today1
not blocked20
Exploited2
Working exploit published1
Proof of concept only4
Forecast only2
No public exploit12
Q3 2463
Protected by Waratek2
No exploit published27
Outside Waratek scope2
Not applicable32
Critical2
High11
Medium43
Low7
blocked by ARMR today2
not blocked61
Exploited2
No public exploit61
Q4 241
Not applicable1
Critical1
not blocked1
No public exploit1
Q1 251
Not applicable1
High1
not blocked1
No public exploit1
Q3 22Q4 22Q1 23Q2 23Q3 23Q4 23Q1 24Q2 24Q3 24Q4 24Q1 25
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-40152 | High | 2022-09-16 | No exploit published | Proof of concept only | Those using Woodstox to parse XML data may be vulnerable to Denial of Service attacks (DOS) if DTD support is enabled. If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow. This effect may support a denial of service attack. |
| CVE-2022-40150 | High | 2022-09-16 | No exploit published | No public exploit | Those using Jettison to parse untrusted XML or JSON data may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by Out of memory. This effect may support a denial of service attack. |
| CVE-2022-40149 | High | 2022-09-16 | No exploit published | No public exploit | Those using Jettison to parse untrusted XML or JSON data may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow. This effect may support a denial of service attack. |
| CVE-2022-36033 | Medium | 2022-08-29 | Protected by Waratek | Proof of concept only | jsoup is a Java HTML parser, built for HTML editing, cleaning, scraping, and cross-site scripting (XSS) safety. jsoup may incorrectly sanitize HTML including `javascript:` URL expressions, which could allow XSS attacks when a reader subsequently clicks that link. If the non-default `SafeList.preserveRelativeLinks` option is enabled, HTML including `javascript:` URLs that have been crafted with control characters will not be sanitized. If the site that this HTML is published on does not set a Content Security Policy, an XSS attack is then possible. This issue is patched in jsoup 1.15.3. Users should upgrade to this version. Additionally, as the unsanitized input may have been persisted, old content should be cleaned again using the updated version. To remediate this issue without immediately upgrading: - disable `SafeList.preserveRelativeLinks`, which will rewrite input URLs as absolute URLs - ensure an appropriate [Content Security Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) is defined. (This should be used regardless of upgrading, as a defence-in-depth best practice.) |
| CVE-2022-37434 | Critical | 2022-08-05 | Not applicable | Proof of concept only | zlib through 1.2.12 has a heap-based buffer over-read or buffer overflow in inflate in inflate.c via a large gzip header extra field. NOTE: only applications that call inflateGetHeader are affected. Some common applications bundle the affected zlib source code but may be unable to call inflateGetHeader (e.g., see the nodejs/node reference). |