Oracle Critical Patch Update January 2022
Released January 2022 · Oracle's advisory ↗ · ← Critical Patch Update, October 2021 · Critical Patch Update, April 2022 →
266 CVEs in this release, one square each
By status
34Protected by Waratek5Mitigation candidate108No exploit published2Outside Waratek scope117Not applicable
13Exploited, marked by the ring
No exploit published. For 74 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 · 18 protected · 7 exploited · 1 CISA KEV · 5 public PoC · 7 EPSS ≥ 0.5
Protected by Waratek
18
17.8%
Rule in development
0
0.0%
Mitigation candidate
1
1.0%
No exploit published
82
81.2%
blocked by ARMR today
18
17.8%
partly blocked
0
0.0%
not blocked
83
82.2%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
7
6.9%
Working exploit published
0
0.0%
Proof of concept only
1
1.0%
Forecast only
1
1.0%
No public exploit
92
91.1%
split by
peak 82 / month
Jul 217
Protected by Waratek1
No exploit published6
High3
Medium4
blocked by ARMR today1
not blocked6
Exploited1
Forecast only1
No public exploit5
Aug 215
No exploit published5
Critical1
High4
not blocked5
No public exploit5
Sep 211
Mitigation candidate1
Medium1
not blocked1
Exploited1
Oct 213
Protected by Waratek2
No exploit published1
Critical1
High2
blocked by ARMR today2
not blocked1
No public exploit3
Nov 210
Dec 213
Protected by Waratek3
High1
Medium2
blocked by ARMR today3
Exploited3
Jan 2282
Protected by Waratek12
No exploit published70
Critical8
High13
Medium57
Low4
blocked by ARMR today12
not blocked70
Exploited2
Proof of concept only1
No public exploit79
Jul 21Aug 21Sep 21Oct 21Nov 21Dec 21Jan 22
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2021-30639 | High | 2021-07-12 | No exploit published | No public exploit | A vulnerability in Apache Tomcat allows an attacker to remotely trigger a denial of service. An error introduced as part of a change to improve error handling during non-blocking I/O meant that the error flag associated with the Request object was not reset between requests. This meant that once a non-blocking I/O error occurred, all future requests handled by that request object would fail. Users were able to trigger non-blocking I/O errors, e.g. by dropping a connection, thereby creating the possibility of triggering a DoS. Applications that do not use non-blocking I/O are not exposed to this vulnerability. This issue affects Apache Tomcat 10.0.3 to 10.0.4; 9.0.44; 8.5.64. |