Oracle Critical Patch Update July 2022
Released July 2022 · Oracle's advisory ↗ · ← Critical Patch Update, April 2022 · Critical Patch Update, October 2022 →
188 CVEs in this release, one square each
By status
27Protected by Waratek10Mitigation candidate83No exploit published2Outside Waratek scope66Not applicable
12Exploited, marked by the ring
No exploit published. For 50 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 · 19 protected · 8 exploited · 3 CISA KEV · 13 public PoC · 12 EPSS ≥ 0.5
Protected by Waratek
19
18.8%
Rule in development
0
0.0%
Mitigation candidate
7
6.9%
No exploit published
75
74.3%
blocked by ARMR today
19
18.8%
partly blocked
0
0.0%
not blocked
82
81.2%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 45 / month
Feb 213
No exploit published3
Critical1
High2
not blocked3
No public exploit3
Mar 210
Apr 212
Protected by Waratek1
No exploit published1
Critical1
Medium1
blocked by ARMR today1
not blocked1
No public exploit2
May 212
Protected by Waratek1
Mitigation candidate1
High2
blocked by ARMR today1
not blocked1
Working exploit published1
No public exploit1
Jun 214
Protected by Waratek1
No exploit published3
High3
Medium1
blocked by ARMR today1
not blocked3
No public exploit4
Jul 215
Protected by Waratek1
No exploit published4
High2
Medium3
blocked by ARMR today1
not blocked4
Exploited1
No public exploit4
Aug 213
No exploit published3
High2
Medium1
not blocked3
No public exploit3
Sep 213
Mitigation candidate1
No exploit published2
Critical1
High1
Medium1
not blocked3
Exploited1
Forecast only1
No public exploit1
Oct 215
Protected by Waratek2
Mitigation candidate1
No exploit published2
Critical1
High2
Medium2
blocked by ARMR today2
not blocked3
Proof of concept only1
No public exploit4
Nov 210
Dec 213
Protected by Waratek1
No exploit published2
Critical1
Medium2
blocked by ARMR today1
not blocked2
Exploited1
No public exploit2
Jan 223
Protected by Waratek2
No exploit published1
Critical1
High1
Medium1
blocked by ARMR today2
not blocked1
Proof of concept only1
No public exploit2
Feb 222
No exploit published2
High1
Medium1
not blocked2
Proof of concept only1
No public exploit1
Mar 224
Protected by Waratek1
Mitigation candidate1
No exploit published2
Critical2
High2
blocked by ARMR today1
not blocked3
Exploited1
No public exploit3
Apr 228
Protected by Waratek5
No exploit published3
Critical4
High1
Medium3
blocked by ARMR today5
not blocked3
Exploited3
Proof of concept only1
No public exploit4
May 228
Protected by Waratek3
Mitigation candidate2
No exploit published3
Critical1
High4
Medium3
blocked by ARMR today3
not blocked5
Exploited1
Working exploit published1
Proof of concept only2
No public exploit4
Jun 221
Mitigation candidate1
Critical1
not blocked1
Proof of concept only1
Jul 2245
Protected by Waratek1
No exploit published44
Critical1
High11
Medium33
blocked by ARMR today1
not blocked44
Proof of concept only1
No public exploit44
Mar 21May 21Jul 21Sep 21Nov 21Jan 22Mar 22May 22Jul 22
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2020-14343 | Critical | 2021-02-09 | No exploit published | No public exploit | A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747. |