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 102 matches · 75 in Waratek scope · 26 protected · 12 exploited · 5 CISA KEV · 21 public PoC · 19 EPSS ≥ 0.5
102matches
75in Waratek scope73.5%
26protected25.5%
12exploited11.8%
5CISA KEV4.9%
21public PoC20.6%
19EPSS ≥ 0.518.6%
Protected by Waratek
26
25.5%
Rule in development
0
0.0%
Mitigation candidate
10
9.8%
No exploit published
39
38.2%
Outside Waratek scope
0
0.0%
Not applicable
27
26.5%
Withdrawn CVE
0
0.0%
blocked by ARMR today
26
25.5%
partly blocked
0
0.0%
not blocked
76
74.5%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 21 / quarter
Q2 181
Protected by Waratek1
Critical1
blocked by ARMR today1
Exploited1
Q3 180
Q4 180
Q1 190
Q2 192
Mitigation candidate1
Not applicable1
High1
Medium1
not blocked2
Working exploit published1
No public exploit1
Q3 192
Protected by Waratek1
No exploit published1
Critical1
High1
blocked by ARMR today1
not blocked1
No public exploit2
Q4 191
No exploit published1
Critical1
not blocked1
No public exploit1
Q1 202
No exploit published2
Critical1
High1
not blocked2
No public exploit2
Q2 205
Protected by Waratek2
Mitigation candidate2
No exploit published1
Critical1
Medium4
blocked by ARMR today2
not blocked3
Exploited2
Working exploit published1
Forecast only1
No public exploit1
Q3 202
Protected by Waratek1
Not applicable1
High2
blocked by ARMR today1
not blocked1
No public exploit2
Q4 204
Protected by Waratek2
No exploit published2
High3
Medium1
blocked by ARMR today2
not blocked2
No public exploit4
Q1 218
Protected by Waratek1
No exploit published4
Not applicable3
Critical3
High5
blocked by ARMR today1
not blocked7
Exploited1
Proof of concept only1
No public exploit6
Q2 218
Protected by Waratek3
Mitigation candidate1
No exploit published4
Critical1
High5
Medium2
blocked by ARMR today3
not blocked5
Working exploit published1
No public exploit7
Q3 2115
Protected by Waratek1
Mitigation candidate1
No exploit published9
Not applicable4
Critical2
High8
Medium5
blocked by ARMR today1
not blocked14
Exploited2
Proof of concept only1
Forecast only1
No public exploit11
Q4 2110
Protected by Waratek3
Mitigation candidate1
No exploit published4
Not applicable2
Critical2
High2
Medium6
blocked by ARMR today3
not blocked7
Exploited1
Proof of concept only1
No public exploit8
Q1 2221
Protected by Waratek3
Mitigation candidate1
No exploit published5
Not applicable12
Critical5
High13
Medium3
blocked by ARMR today3
not blocked18
Exploited1
Proof of concept only6
No public exploit14
Q2 2221
Protected by Waratek8
Mitigation candidate3
No exploit published6
Not applicable4
Critical7
High8
Medium6
blocked by ARMR today8
not blocked13
Exploited4
Working exploit published1
Proof of concept only6
No public exploit10
Q2 18Q4 18Q2 19Q4 19Q2 20Q4 20Q2 21Q4 21Q2 22
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2019-0227 | High | 2019-05-01 | Mitigation candidate | Working exploit published | A Server Side Request Forgery (SSRF) vulnerability affected the Apache Axis 1.4 distribution that was last released in 2006. Security and bug commits commits continue in the projects Axis 1.x Subversion repository, legacy users are encouraged to build from source. The successor to Axis 1.x is Axis2, the latest version is 1.7.9 and is not vulnerable to this issue. |
| CVE-2018-1273 | Critical | 2018-04-11 | Protected by Waratek | Exploited | Spring Data Commons, versions prior to 1.13 to 1.13.10, 2.0 to 2.0.5, and older unsupported versions, contain a property binder vulnerability caused by improper neutralization of special elements. An unauthenticated remote malicious user (or attacker) can supply specially crafted request parameters against Spring Data REST backed HTTP resources or using Spring Data's projection-based request payload binding hat can lead to a remote code execution attack. |