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 105 matches · 0 protected · 5 exploited · 2 CISA KEV · 8 public PoC · 7 EPSS ≥ 0.5
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
9
8.6%
No exploit published
96
91.4%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
105
100.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 34 / quarter
Q2 191
Mitigation candidate1
High1
not blocked1
Working exploit published1
Q3 191
No exploit published1
Medium1
not blocked1
No public exploit1
Q4 191
Mitigation candidate1
Critical1
not blocked1
Proof of concept only1
Q1 204
No exploit published4
High3
Medium1
not blocked4
Proof of concept only1
No public exploit3
Q2 204
Mitigation candidate1
No exploit published3
High2
Medium1
Low1
not blocked4
Exploited1
No public exploit3
Q3 201
No exploit published1
Medium1
not blocked1
No public exploit1
Q4 208
No exploit published8
High5
Medium2
Low1
not blocked8
No public exploit8
Q1 2111
Mitigation candidate1
No exploit published10
Critical2
High2
Medium7
not blocked11
Exploited1
No public exploit10
Q2 217
Mitigation candidate1
No exploit published6
Critical1
High1
Medium5
not blocked7
Exploited1
No public exploit6
Q3 2113
Mitigation candidate1
No exploit published12
High7
Medium6
not blocked13
Exploited1
Forecast only1
No public exploit11
Q4 219
Mitigation candidate2
No exploit published7
Critical2
High2
Medium5
not blocked9
Proof of concept only2
No public exploit7
Q1 2210
Mitigation candidate1
No exploit published9
Critical1
High3
Medium6
not blocked10
Exploited1
Proof of concept only2
Forecast only1
No public exploit6
Q2 2234
No exploit published34
Critical2
High9
Medium23
not blocked34
No public exploit34
Q3 221
No exploit published1
High1
not blocked1
No public exploit1
Q3 19Q1 20Q3 20Q1 21Q3 21Q1 22Q3 22
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2019-12399 | High | 2020-01-14 | No exploit published | No public exploit | When Connect workers in Apache Kafka 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.2.0, 2.2.1, or 2.3.0 are configured with one or more config providers, and a connector is created/updated on that Connect cluster to use an externalized secret variable in a substring of a connector configuration property value, then any client can issue a request to the same Connect cluster to obtain the connector's task configuration and the response will contain the plaintext secret rather than the externalized secrets variables. |
| CVE-2019-14862 | Medium | 2020-01-02 | No exploit published | No public exploit | There is a vulnerability in knockout before version 3.5.0-beta, where after escaping the context of the web application, the web application delivers data to its users along with other trusted dynamic content, without validating it. |
| CVE-2019-17195 | Critical | 2019-10-15 | Mitigation candidate | Proof of concept only | Connect2id Nimbus JOSE+JWT before v7.9 can throw various uncaught exceptions while parsing a JWT, which could result in an application crash (potential information disclosure) or a potential authentication bypass. |
| CVE-2019-3740 | Medium | 2019-09-18 | No exploit published | No public exploit | RSA BSAFE Crypto-J versions prior to 6.2.5 are vulnerable to an Information Exposure Through Timing Discrepancy vulnerabilities during DSA key generation. A malicious remote attacker could potentially exploit those vulnerabilities to recover DSA keys. |
| 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. |