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 112 matches · 59 in Waratek scope · 11 protected · 4 exploited · 3 CISA KEV · 8 public PoC · 14 EPSS ≥ 0.5
112matches
59in Waratek scope52.7%
11protected9.8%
4exploited3.6%
3CISA KEV2.7%
8public PoC7.1%
14EPSS ≥ 0.512.5%
Protected by Waratek
11
9.8%
Rule in development
0
0.0%
Mitigation candidate
1
0.9%
No exploit published
47
42.0%
Outside Waratek scope
0
0.0%
Not applicable
53
47.3%
Withdrawn CVE
0
0.0%
blocked by ARMR today
11
9.8%
partly blocked
0
0.0%
not blocked
101
90.2%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 86 / month
Dec 216
Protected by Waratek1
No exploit published3
Not applicable2
Critical3
High1
Medium2
blocked by ARMR today1
not blocked5
Exploited1
Working exploit published1
Forecast only1
No public exploit3
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
Dec 21Jan 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. |
| CVE-2021-44832 | Medium | 2021-12-28 | Protected by Waratek | Exploited | Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a remote code execution (RCE) attack when a configuration uses a JDBC Appender with a JNDI LDAP data source URI when an attacker has control of the target LDAP server. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2. |
| CVE-2021-44790 | Critical | 2021-12-20 | Not applicable | Working exploit published | A carefully crafted request body can cause a buffer overflow in the mod_lua multipart parser (r:parsebody() called from Lua scripts). The Apache httpd team is not aware of an exploit for the vulnerabilty though it might be possible to craft one. This issue affects Apache HTTP Server 2.4.51 and earlier. |
| CVE-2021-44224 | High | 2021-12-20 | Not applicable | Forecast only | A crafted URI sent to httpd configured as a forward proxy (ProxyRequests on) can cause a crash (NULL pointer dereference) or, for configurations mixing forward and reverse proxy declarations, can allow for requests to be directed to a declared Unix Domain Socket endpoint (Server Side Request Forgery). This issue affects Apache HTTP Server 2.4.7 up to 2.4.51 (included). |
| CVE-2021-23450 | Critical | 2021-12-17 | No exploit published | No public exploit | All versions of package dojo are vulnerable to Prototype Pollution via the setObject function. |
| CVE-2021-43797 | Medium | 2021-12-09 | No exploit published | No public exploit | Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. Netty prior to version 4.1.71.Final skips control chars when they are present at the beginning / end of the header name. It should instead fail fast as these are not allowed by the spec and could lead to HTTP request smuggling. Failing to do the validation might cause netty to "sanitize" header names before it forward these to another remote system when used as proxy. This remote system can't see the invalid usage anymore, and therefore does not do the validation itself. Users should upgrade to version 4.1.71.Final. |
| CVE-2021-43527 | Critical | 2021-12-08 | No exploit published | No public exploit | NSS (Network Security Services) versions prior to 3.73 or 3.68.1 ESR are vulnerable to a heap overflow when handling DER-encoded DSA or RSA-PSS signatures. Applications using NSS for handling signatures encoded within CMS, S/MIME, PKCS \#7, or PKCS \#12 are likely to be impacted. Applications using NSS for certificate validation or other TLS, X.509, OCSP or CRL functionality may be impacted, depending on how they configure NSS. *Note: This vulnerability does NOT impact Mozilla Firefox.* However, email clients and PDF viewers that use NSS for signature verification, such as Thunderbird, LibreOffice, Evolution and Evince are believed to be impacted. This vulnerability affects NSS < 3.73 and NSS < 3.68.1. |