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 107 matches · 65 in Waratek scope · 12 protected · 5 exploited · 3 CISA KEV · 12 public PoC · 8 EPSS ≥ 0.5
107matches
65in Waratek scope60.7%
12protected11.2%
5exploited4.7%
3CISA KEV2.8%
12public PoC11.2%
8EPSS ≥ 0.57.5%
Protected by Waratek
12
11.2%
Rule in development
0
0.0%
Mitigation candidate
3
2.8%
No exploit published
50
46.7%
Outside Waratek scope
4
3.7%
Not applicable
38
35.5%
Withdrawn CVE
0
0.0%
blocked by ARMR today
12
11.2%
partly blocked
0
0.0%
not blocked
95
88.8%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
5
4.7%
Working exploit published
0
0.0%
Proof of concept only
25
23.4%
Forecast only
1
0.9%
No public exploit
76
71.0%
split by
peak 30 / quarter
Q3 191
Protected by Waratek1
High1
blocked by ARMR today1
No public exploit1
Q4 191
No exploit published1
Critical1
not blocked1
No public exploit1
Q1 200
Q2 201
No exploit published1
Medium1
not blocked1
No public exploit1
Q3 200
Q4 201
No exploit published1
Medium1
not blocked1
No public exploit1
Q1 214
Protected by Waratek2
No exploit published1
Not applicable1
Critical2
High1
Medium1
blocked by ARMR today2
not blocked2
No public exploit4
Q2 212
Protected by Waratek1
Outside Waratek scope1
High1
Medium1
blocked by ARMR today1
not blocked1
No public exploit2
Q3 213
No exploit published3
High1
Medium2
not blocked3
No public exploit3
Q4 213
Mitigation candidate1
No exploit published2
Medium3
not blocked3
Proof of concept only1
No public exploit2
Q1 222
Protected by Waratek1
No exploit published1
Critical2
blocked by ARMR today1
not blocked1
Proof of concept only1
No public exploit1
Q2 226
Protected by Waratek2
No exploit published3
Not applicable1
Critical2
Medium3
Low1
blocked by ARMR today2
not blocked4
Exploited1
Proof of concept only1
No public exploit4
Q3 2212
Protected by Waratek3
Mitigation candidate1
No exploit published5
Outside Waratek scope1
Not applicable2
Critical3
High5
Medium4
blocked by ARMR today3
not blocked9
Proof of concept only8
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 248
Protected by Waratek1
No exploit published1
Not applicable6
Critical1
High2
Medium5
blocked by ARMR today1
not blocked7
Exploited1
Forecast only1
No public exploit6
Q3 19Q1 20Q3 20Q1 21Q3 21Q1 22Q3 22Q1 23Q3 23Q1 24
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2020-11987 | High | 2021-02-24 | No exploit published | No public exploit | Apache Batik 1.13 is vulnerable to server-side request forgery, caused by improper input validation by the NodePickerPanel. By using a specially-crafted argument, an attacker could exploit this vulnerability to cause the underlying server to make arbitrary GET requests. |
| CVE-2021-27568 | Medium | 2021-02-23 | Protected by Waratek | No public exploit | An issue was discovered in netplex json-smart-v1 through 2015-10-23 and json-smart-v2 through 2.4. An exception is thrown from a function, but it is not caught, as demonstrated by NumberFormatException. When it is not caught, it may cause programs using the library to crash or expose sensitive information. |
| CVE-2021-23926 | Critical | 2021-01-14 | Protected by Waratek | No public exploit | The XML parsers used by XMLBeans up to version 2.6.0 did not set the properties needed to protect the user from malicious XML input. Vulnerabilities include possibilities for XML Entity Expansion attacks. Affects XMLBeans up to and including v2.6.0. |
| CVE-2020-13956 | Medium | 2020-12-02 | No exploit published | No public exploit | Apache HttpClient versions prior to version 4.5.13 and 5.0.3 can misinterpret malformed authority component in request URIs passed to the library as java.net.URI object and pick the wrong target host for request execution. |
| CVE-2020-1945 | Medium | 2020-05-14 | No exploit published | No public exploit | Apache Ant 1.1 to 1.9.14 and 1.10.0 to 1.10.7 uses the default temporary directory identified by the Java system property java.io.tmpdir for several tasks and may thus leak sensitive information. The fixcrlf and replaceregexp tasks also copy files from the temporary directory back into the build tree allowing an attacker to inject modified source files into the build process. |
| CVE-2019-17267 | Critical | 2019-10-07 | No exploit published | No public exploit | A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10. It is related to net.sf.ehcache.hibernate.EhcacheJtaTransactionManagerLookup. |
| CVE-2019-10086 | High | 2019-08-20 | Protected by Waratek | No public exploit | In Apache Commons Beanutils 1.9.2, a special BeanIntrospector class was added which allows suppressing the ability for an attacker to access the classloader via the class property available on all Java objects. We, however were not using this by default characteristic of the PropertyUtilsBean. |