Oracle Critical Patch Update July 2023
Released July 2023 · Oracle's advisory ↗ · ← Critical Patch Update, April 2023 · Critical Patch Update, October 2023 →
269 CVEs in this release, one square each
By status
46Protected by Waratek7Mitigation candidate112No exploit published6Outside Waratek scope98Not applicable
12Exploited, marked by the ring
No exploit published. For 37 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 208 matches · 113 in Waratek scope · 24 protected · 6 exploited · 0 CISA KEV · 15 public PoC · 11 EPSS ≥ 0.5
208matches
113in Waratek scope54.3%
24protected11.5%
6exploited2.9%
0CISA KEV0.0%
15public PoC7.2%
11EPSS ≥ 0.55.3%
Protected by Waratek
24
11.5%
Rule in development
0
0.0%
Mitigation candidate
5
2.4%
No exploit published
84
40.4%
Outside Waratek scope
6
2.9%
Not applicable
89
42.8%
Withdrawn CVE
0
0.0%
blocked by ARMR today
24
11.5%
partly blocked
0
0.0%
not blocked
184
88.5%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 56 / month
Apr 228
Protected by Waratek3
No exploit published2
Not applicable3
Critical3
High3
Medium2
blocked by ARMR today3
not blocked5
Proof of concept only2
No public exploit6
May 224
Protected by Waratek2
No exploit published1
Not applicable1
Critical1
High1
Medium2
blocked by ARMR today2
not blocked2
Proof of concept only1
No public exploit3
Jun 222
Protected by Waratek1
No exploit published1
Medium1
Low1
blocked by ARMR today1
not blocked1
Exploited1
No public exploit1
Jul 2214
Mitigation candidate1
No exploit published6
Outside Waratek scope1
Not applicable6
Critical7
High5
Medium1
Low1
not blocked14
Proof of concept only3
No public exploit11
Aug 223
Protected by Waratek2
Not applicable1
Critical1
High1
Medium1
blocked by ARMR today2
not blocked1
Exploited1
Proof of concept only2
Sep 2213
Protected by Waratek3
Mitigation candidate1
No exploit published6
Not applicable3
Critical1
High7
Medium5
blocked by ARMR today3
not blocked10
Proof of concept only5
No public exploit8
Oct 2212
Protected by Waratek2
Mitigation candidate1
No exploit published5
Not applicable4
Critical3
High9
blocked by ARMR today2
not blocked10
Proof of concept only3
No public exploit9
Nov 2211
Protected by Waratek4
No exploit published2
Not applicable5
Critical3
High7
Medium1
blocked by ARMR today4
not blocked7
Proof of concept only4
No public exploit7
Dec 2217
Protected by Waratek1
Mitigation candidate1
No exploit published8
Outside Waratek scope1
Not applicable6
Critical2
High11
Medium4
blocked by ARMR today1
not blocked16
Exploited1
Proof of concept only7
No public exploit9
Jan 2312
Protected by Waratek2
No exploit published4
Not applicable6
Critical1
High4
Medium6
Low1
blocked by ARMR today2
not blocked10
Exploited1
Proof of concept only1
Forecast only1
No public exploit9
Feb 2317
Protected by Waratek1
No exploit published1
Not applicable15
Critical1
High10
Medium6
blocked by ARMR today1
not blocked16
Exploited1
Proof of concept only4
Forecast only1
No public exploit11
Mar 2320
Protected by Waratek1
No exploit published12
Not applicable7
Critical2
High10
Medium8
blocked by ARMR today1
not blocked19
Exploited1
Proof of concept only2
No public exploit17
Apr 2314
Protected by Waratek1
No exploit published7
Not applicable6
Critical2
High3
Medium9
blocked by ARMR today1
not blocked13
Proof of concept only1
Forecast only1
No public exploit12
May 233
No exploit published1
Not applicable2
High2
Medium1
not blocked3
Forecast only1
No public exploit2
Jun 232
Not applicable2
High2
not blocked2
No public exploit2
Jul 2356
Protected by Waratek1
Mitigation candidate1
No exploit published28
Outside Waratek scope4
Not applicable22
Critical2
High6
Medium37
Low11
blocked by ARMR today1
not blocked55
Working exploit published1
No public exploit55
May 22Jul 22Sep 22Nov 22Jan 23Mar 23May 23Jul 23
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-24891 | Medium | 2022-04-27 | No exploit published | Proof of concept only | ESAPI (The OWASP Enterprise Security API) is a free, open source, web application security control library. Prior to version 2.3.0.0, there is a potential for a cross-site scripting vulnerability in ESAPI caused by a incorrect regular expression for "onsiteURL" in the **antisamy-esapi.xml** configuration file that can cause "javascript:" URLs to fail to be correctly sanitized. This issue is patched in ESAPI 2.3.0.0. As a workaround, manually edit the **antisamy-esapi.xml** configuration files to change the "onsiteURL" regular expression. More information about remediation of the vulnerability, including the workaround, is available in the maintainers' release notes and security bulletin. |
| CVE-2022-29546 | High | 2022-04-25 | No exploit published | No public exploit | HtmlUnit NekoHtml Parser before 2.61.0 suffers from a denial of service vulnerability. Crafted input associated with the parsing of Processing Instruction (PI) data leads to heap memory consumption. This is similar to CVE-2022-28366 but affects a much later version of the product. |
| CVE-2022-23457 | Critical | 2022-04-25 | Protected by Waratek | Proof of concept only | ESAPI (The OWASP Enterprise Security API) is a free, open source, web application security control library. Prior to version 2.3.0.0, the default implementation of `Validator.getValidDirectoryPath(String, String, File, boolean)` may incorrectly treat the tested input string as a child of the specified parent directory. This potentially could allow control-flow bypass checks to be defeated if an attack can specify the entire string representing the 'input' path. This vulnerability is patched in release 2.3.0.0 of ESAPI. As a workaround, it is possible to write one's own implementation of the Validator interface. However, maintainers do not recommend this. |
| CVE-2022-27406 | High | 2022-04-22 | Not applicable | No public exploit | FreeType commit 22a0cccb4d9d002f33c1ba7a4b36812c7d4f46b5 was discovered to contain a segmentation violation via the function FT_Request_Size. |
| CVE-2022-27405 | High | 2022-04-22 | Not applicable | No public exploit | FreeType commit 53dfdcd8198d2b3201a23c4bad9190519ba918db was discovered to contain a segmentation violation via the function FNT_Size_Request. |
| CVE-2022-27404 | Critical | 2022-04-22 | Not applicable | No public exploit | FreeType commit 1e2eb65048f75c64b68708efed6ce904c31f3b2f was discovered to contain a heap buffer overflow via the function sfnt_init_face. |
| CVE-2022-26612 | Critical | 2022-04-07 | Protected by Waratek | No public exploit | In Apache Hadoop, The unTar function uses unTarUsingJava function on Windows and the built-in tar utility on Unix and other OSes. As a result, a TAR entry may create a symlink under the expected extraction directory which points to an external directory. A subsequent TAR entry may extract an arbitrary file into the external directory using the symlink name. This however would be caught by the same targetDirPath check on Unix because of the getCanonicalPath call. However on Windows, getCanonicalPath doesn't resolve symbolic links, which bypasses the check. unpackEntries during TAR extraction follows symbolic links which allows writing outside expected base directory on Windows. This was addressed in Apache Hadoop 3.2.3 |
| CVE-2022-22950 | Medium | 2022-04-01 | Protected by Waratek | No public exploit | n Spring Framework versions 5.3.0 - 5.3.16 and older unsupported versions, it is possible for a user to provide a specially crafted SpEL expression that may cause a denial of service condition. |