Oracle Critical Patch Update April 2022
Released April 2022 · Oracle's advisory ↗ · ← Critical Patch Update, January 2022 · Critical Patch Update, July 2022 →
222 CVEs in this release, one square each
By status
29Protected by Waratek9Mitigation candidate96No exploit published88Not applicable
13Exploited, marked by the ring
No exploit published. For 46 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 106 matches · 55 in Waratek scope · 10 protected · 3 exploited · 3 CISA KEV · 7 public PoC · 11 EPSS ≥ 0.5
106matches
55in Waratek scope51.9%
10protected9.4%
3exploited2.8%
3CISA KEV2.8%
7public PoC6.6%
11EPSS ≥ 0.510.4%
Protected by Waratek
10
9.4%
Rule in development
0
0.0%
Mitigation candidate
1
0.9%
No exploit published
44
41.5%
Outside Waratek scope
0
0.0%
Not applicable
51
48.1%
Withdrawn CVE
0
0.0%
blocked by ARMR today
10
9.4%
partly blocked
0
0.0%
not blocked
96
90.6%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 86 / month
Jan 2212
Protected by Waratek4
No exploit published6
Not applicable2
Critical3
High3
Medium6
blocked by ARMR today4
not blocked8
Working exploit published1
Proof of concept only3
Forecast only1
No public exploit7
Feb 223
No exploit published2
Not applicable1
High1
Medium2
not blocked3
Proof of concept only1
No public exploit2
Mar 223
Mitigation candidate1
No exploit published1
Not applicable1
Critical1
High2
not blocked3
Exploited1
Proof of concept only1
No public exploit1
Apr 2286
Protected by Waratek6
No exploit published34
Not applicable46
Critical4
High15
Medium60
Low7
blocked by ARMR today6
not blocked80
Exploited2
Proof of concept only1
Forecast only2
No public exploit81
May 220
Jun 220
Jul 220
Aug 222
No exploit published1
Not applicable1
High1
Medium1
not blocked2
No public exploit2
Jan 22Feb 22Mar 22Apr 22May 22Jun 22Jul 22Aug 22
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-23305 | Critical | 2022-01-18 | Protected by Waratek | Proof of concept only | By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions. |
| CVE-2022-20615 | Medium | 2022-01-12 | No exploit published | Forecast only | Jenkins Matrix Project Plugin 1.19 and earlier does not escape HTML metacharacters in node and label names, and label descriptions, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Agent/Configure permission. |
| CVE-2022-20613 | Medium | 2022-01-12 | No exploit published | No public exploit | A cross-site request forgery (CSRF) vulnerability in Jenkins Mailer Plugin 391.ve4a_38c1b_cf4b_ and earlier allows attackers to use the DNS used by the Jenkins instance to resolve an attacker-specified hostname. |
| CVE-2022-20612 | Medium | 2022-01-12 | No exploit published | No public exploit | A cross-site request forgery (CSRF) vulnerability in Jenkins 2.329 and earlier, LTS 2.319.1 and earlier allows attackers to trigger build of job without parameters when no security realm is set. |
| CVE-2021-42392 | Critical | 2022-01-10 | Protected by Waratek | Working exploit published | The org.h2.util.JdbcUtils.getConnection method of the H2 database takes as parameters the class name of the driver and URL of the database. An attacker may pass a JNDI driver name and a URL leading to a LDAP or RMI servers, causing remote code execution. This can be exploited through various attack vectors, most notably through the H2 Console which leads to unauthenticated remote code execution. |
| CVE-2021-22569 | High | 2022-01-10 | No exploit published | Proof of concept only | An issue in protobuf-java allowed the interleaving of com.google.protobuf.UnknownFieldSet fields in such a way that would be processed out of order. A small malicious payload can occupy the parser for several minutes by creating large numbers of short-lived objects that cause frequent, repeated pauses. We recommend upgrading libraries beyond the vulnerable versions. |