Oracle Critical Patch Update January 2024
Released January 2024 · Oracle's advisory ↗ · ← Critical Patch Update, October 2023 · Critical Patch Update, April 2024 →
236 CVEs in this release, one square each
By status
27Protected by Waratek4Mitigation candidate101No exploit published26Outside Waratek scope78Not applicable
9Exploited, marked by the ring
No exploit published. For 47 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 109 matches · 54 in Waratek scope · 7 protected · 0 exploited · 0 CISA KEV · 2 public PoC · 1 EPSS ≥ 0.5
109matches
54in Waratek scope49.5%
7protected6.4%
0exploited0.0%
0CISA KEV0.0%
2public PoC1.8%
1EPSS ≥ 0.50.9%
Protected by Waratek
7
6.4%
Rule in development
0
0.0%
Mitigation candidate
1
0.9%
No exploit published
46
42.2%
Outside Waratek scope
18
16.5%
Not applicable
37
33.9%
Withdrawn CVE
0
0.0%
blocked by ARMR today
7
6.4%
partly blocked
0
0.0%
not blocked
102
93.6%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 63 / quarter
Q3 201
No exploit published1
Medium1
not blocked1
No public exploit1
Q4 202
Protected by Waratek1
Not applicable1
Medium2
blocked by ARMR today1
not blocked1
No public exploit2
Q1 210
Q2 211
Protected by Waratek1
Medium1
blocked by ARMR today1
No public exploit1
Q3 210
Q4 213
Outside Waratek scope3
Medium3
not blocked3
Proof of concept only1
No public exploit2
Q1 220
Q2 221
No exploit published1
Medium1
not blocked1
No public exploit1
Q3 222
Protected by Waratek1
Outside Waratek scope1
Medium2
blocked by ARMR today1
not blocked1
Proof of concept only2
Q4 221
No exploit published1
Medium1
not blocked1
No public exploit1
Q1 238
Not applicable8
Medium8
not blocked8
Proof of concept only1
No public exploit7
Q2 235
No exploit published1
Not applicable4
Medium5
not blocked5
Forecast only1
No public exploit4
Q3 2315
Protected by Waratek1
No exploit published8
Outside Waratek scope1
Not applicable5
Medium15
blocked by ARMR today1
not blocked14
No public exploit15
Q4 237
Protected by Waratek1
Mitigation candidate1
No exploit published4
Not applicable1
Medium7
blocked by ARMR today1
not blocked6
Working exploit published1
No public exploit6
Q1 2463
Protected by Waratek2
No exploit published30
Outside Waratek scope13
Not applicable18
Medium63
blocked by ARMR today2
not blocked61
No public exploit63
Q3 20Q1 21Q3 21Q1 22Q3 22Q1 23Q3 23Q1 24
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-31160 | Medium | 2022-07-20 | Outside Waratek scope | Proof of concept only | jQuery UI is a curated set of user interface interactions, effects, widgets, and themes built on top of jQuery. Versions prior to 1.13.2 are potentially vulnerable to cross-site scripting. Initializing a checkboxradio widget on an input enclosed within a label makes that parent label contents considered as the input label. Calling `.checkboxradio( "refresh" )` on such a widget and the initial HTML contained encoded HTML entities will make them erroneously get decoded. This can lead to potentially executing JavaScript code. The bug has been patched in jQuery UI 1.13.2. To remediate the issue, someone who can change the initial HTML can wrap all the non-input contents of the `label` in a `span`. |
| CVE-2022-22969 | Medium | 2022-04-21 | No exploit published | No public exploit | <Issue Description> Spring Security OAuth versions 2.5.x prior to 2.5.2 and older unsupported versions are susceptible to a Denial-of-Service (DoS) attack via the initiation of the Authorization Request in an OAuth 2.0 Client application. A malicious user or attacker can send multiple requests initiating the Authorization Request for the Authorization Code Grant, which has the potential of exhausting system resources using a single session. This vulnerability exposes OAuth 2.0 Client applications only. |
| CVE-2021-41184 | Medium | 2021-10-26 | Outside Waratek scope | Proof of concept only | jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of the `of` option of the `.position()` util from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `of` option is now treated as a CSS selector. A workaround is to not accept the value of the `of` option from untrusted sources. |
| CVE-2021-41183 | Medium | 2021-10-26 | Outside Waratek scope | No public exploit | jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of various `*Text` options of the Datepicker widget from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. The values passed to various `*Text` options are now always treated as pure text, not HTML. A workaround is to not accept the value of the `*Text` options from untrusted sources. |
| CVE-2021-41182 | Medium | 2021-10-26 | Outside Waratek scope | No public exploit | jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of the `altField` option of the Datepicker widget from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `altField` option is now treated as a CSS selector. A workaround is to not accept the value of the `altField` option from untrusted sources. |
| CVE-2021-29425 | Medium | 2021-04-13 | Protected by Waratek | No public exploit | In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like "//../foo", or "\\..\foo", the result would be the same value, thus possibly providing access to files in the parent directory, but not further above (thus "limited" path traversal), if the calling code would use the result to construct a path value. |
| CVE-2020-15250 | Medium | 2020-10-12 | Protected by Waratek | No public exploit | In JUnit4 from version 4.7 and before 4.13.1, the test rule TemporaryFolder contains a local information disclosure vulnerability. On Unix like systems, the system's temporary directory is shared between all users on that system. Because of this, when files and directories are written into this directory they are, by default, readable by other users on that same system. This vulnerability does not allow other users to overwrite the contents of these directories or files. This is purely an information disclosure vulnerability. This vulnerability impacts you if the JUnit tests write sensitive information, like API keys or passwords, into the temporary folder, and the JUnit tests execute in an environment where the OS has other untrusted users. Because certain JDK file system APIs were only added in JDK 1.7, this this fix is dependent upon the version of the JDK you are using. For Java 1.7 and higher users: this vulnerability is fixed in 4.13.1. For Java 1.6 and lower users: no patch is available, you must use the workaround below. If you are unable to patch, or are stuck running on Java 1.6, specifying the `java.io.tmpdir` system environment variable to a directory that is exclusively owned by the executing user will fix this vulnerability. For more information, including an example of vulnerable code, see the referenced GitHub Security Advisory. |
| CVE-2020-26870 | Medium | 2020-10-07 | Not applicable | No public exploit | Cure53 DOMPurify before 2.0.17 allows mutation XSS. This occurs because a serialize-parse roundtrip does not necessarily return the original DOM tree, and a namespace can change from HTML to MathML, as demonstrated by nesting of FORM elements. |
| CVE-2020-5421 | Medium | 2020-09-19 | No exploit published | No public exploit | In Spring Framework versions 5.2.0 - 5.2.8, 5.1.0 - 5.1.17, 5.0.0 - 5.0.18, 4.3.0 - 4.3.28, and older unsupported versions, the protections against RFD attacks from CVE-2015-5211 may be bypassed depending on the browser used through the use of a jsessionid path parameter. |