Oracle Critical Patch Update April 2023
Released April 2023 · Oracle's advisory ↗ · ← Critical Patch Update, January 2023 · Critical Patch Update, July 2023 →
328 CVEs in this release, one square each
By status
47Protected by Waratek9Mitigation candidate119No exploit published35Outside Waratek scope118Not applicable
12Exploited, marked by the ring
No exploit published. For 56 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 8 matches · 5 protected · 2 exploited · 1 CISA KEV · 3 EPSS ≥ 0.5
Protected by Waratek
5
62.5%
Rule in development
0
0.0%
Mitigation candidate
3
37.5%
No exploit published
0
0.0%
blocked by ARMR today
5
62.5%
partly blocked
0
0.0%
not blocked
3
37.5%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
2
25.0%
Working exploit published
1
12.5%
Proof of concept only
5
62.5%
Forecast only
0
0.0%
No public exploit
0
0.0%
split by
peak 3 / month
Dec 201
Mitigation candidate1
High1
not blocked1
Proof of concept only1
Jan 213
Protected by Waratek1
Mitigation candidate2
High3
blocked by ARMR today1
not blocked2
Proof of concept only3
Feb 210
Mar 210
Apr 210
May 210
Jun 211
Protected by Waratek1
Medium1
blocked by ARMR today1
Working exploit published1
Jul 210
Aug 210
Sep 210
Oct 210
Nov 210
Dec 211
Protected by Waratek1
High1
blocked by ARMR today1
Exploited1
Jan 221
Protected by Waratek1
Critical1
blocked by ARMR today1
Proof of concept only1
Feb 220
Mar 220
Apr 221
Protected by Waratek1
Critical1
blocked by ARMR today1
Exploited1
Dec 20Feb 21Apr 21Jun 21Aug 21Oct 21Dec 21Feb 22Apr 22
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-22965 | Critical | 2022-04-01 | Protected by Waratek | Exploited | A Spring MVC or Spring WebFlux application running on JDK 9+ may be vulnerable to remote code execution (RCE) via data binding. The specific exploit requires the application to run on Tomcat as a WAR deployment. If the application is deployed as a Spring Boot executable jar, i.e. the default, it is not vulnerable to the exploit. However, the nature of the vulnerability is more general, and there may be other ways to exploit it. |
| 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-2021-4104 | High | 2021-12-14 | Protected by Waratek | Exploited | JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. 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-2020-6950 | Medium | 2021-06-02 | Protected by Waratek | Working exploit published | Directory traversal in Eclipse Mojarra before 2.3.14 allows attackers to read arbitrary files via the loc parameter or con parameter. |
| CVE-2020-36179 | High | 2021-01-07 | Mitigation candidate | Proof of concept only | FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to oadd.org.apache.commons.dbcp.cpdsadapter.DriverAdapterCPDS. |
| CVE-2020-36188 | High | 2021-01-06 | Protected by Waratek | Proof of concept only | FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to com.newrelic.agent.deps.ch.qos.logback.core.db.JNDIConnectionSource. |
| CVE-2020-36184 | High | 2021-01-06 | Mitigation candidate | Proof of concept only | FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp2.datasources.PerUserPoolDataSource. |
| CVE-2020-35728 | High | 2020-12-27 | Mitigation candidate | Proof of concept only | FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to com.oracle.wls.shaded.org.apache.xalan.lib.sql.JNDIConnectionPool (aka embedded Xalan in org.glassfish.web/javax.servlet.jsp.jstl). |