Linux · Red Hat · Security advisory · January 24, 2022

RHSA-2022:0185: Security update for 23 packages

RHSA-2022:0185, released January 24, 2022, fixes 15 CVEs across 23 products. None of them is reported as exploited. Patch Radar priority: Routine.

Routine
CVEs closed
15
None rated Critical
Exploited
0
None reported
Highest CVSS
5.3
Base score, 0 to 10
Highest EPSS
0.0835
94th percentile

Priority of the 15 CVEs

Patch now 0 Urgent 0 High 0 Routine 15

Fixed package versions

ProductReleaseFixed in
java-11-openjdkRHEL 81:11.0.14.0.9-2.el8_5
java-11-openjdk-demoRHEL 81:11.0.14.0.9-2.el8_5
java-11-openjdk-demo-fastdebugRHEL 81:11.0.14.0.9-2.el8_5
java-11-openjdk-demo-slowdebugRHEL 81:11.0.14.0.9-2.el8_5
java-11-openjdk-develRHEL 81:11.0.14.0.9-2.el8_5
java-11-openjdk-devel-fastdebugRHEL 81:11.0.14.0.9-2.el8_5
java-11-openjdk-devel-slowdebugRHEL 81:11.0.14.0.9-2.el8_5
java-11-openjdk-fastdebugRHEL 81:11.0.14.0.9-2.el8_5
java-11-openjdk-headlessRHEL 81:11.0.14.0.9-2.el8_5
java-11-openjdk-headless-fastdebugRHEL 81:11.0.14.0.9-2.el8_5
java-11-openjdk-headless-slowdebugRHEL 81:11.0.14.0.9-2.el8_5
java-11-openjdk-javadocRHEL 81:11.0.14.0.9-2.el8_5
java-11-openjdk-javadoc-zipRHEL 81:11.0.14.0.9-2.el8_5
java-11-openjdk-jmodsRHEL 81:11.0.14.0.9-2.el8_5
java-11-openjdk-jmods-fastdebugRHEL 81:11.0.14.0.9-2.el8_5
java-11-openjdk-jmods-slowdebugRHEL 81:11.0.14.0.9-2.el8_5
java-11-openjdk-slowdebugRHEL 81:11.0.14.0.9-2.el8_5
java-11-openjdk-srcRHEL 81:11.0.14.0.9-2.el8_5
java-11-openjdk-src-fastdebugRHEL 81:11.0.14.0.9-2.el8_5
java-11-openjdk-src-slowdebugRHEL 81:11.0.14.0.9-2.el8_5
java-11-openjdk-static-libsRHEL 81:11.0.14.0.9-2.el8_5
java-11-openjdk-static-libs-fastdebugRHEL 81:11.0.14.0.9-2.el8_5
java-11-openjdk-static-libs-slowdebugRHEL 81:11.0.14.0.9-2.el8_5

CVEs this fix closes

PriorityCVETitleCVSSEPSSExploitation
Routine CVE-2022-21293 Microsoft Build of OpenJDK with Hotspot 11: Uncontrolled Resource Consumption5.3 0.0835 None reported
Routine CVE-2022-21340 Microsoft Build of OpenJDK with Hotspot 11: Uncontrolled Resource Consumption5.3 0.0775 None reported
Routine CVE-2022-21283 Microsoft Build of OpenJDK with Hotspot 11: Protection Mechanism Failure5.3 0.0378 None reported
Routine CVE-2022-21341 Microsoft Build of OpenJDK with Hotspot 11: Deserialization of Untrusted Data5.3 0.0377 None reported
Routine CVE-2022-21248 Microsoft Build of OpenJDK with Hotspot 11: Vulnerability in the Oracle Java SE, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component:…5.3 0.0376 None reported
Routine CVE-2022-21360 Microsoft Build of OpenJDK with Hotspot 11: Uncontrolled Resource Consumption5.3 0.0349 None reported
Routine CVE-2022-21365 Microsoft Build of OpenJDK with Hotspot 11: Vulnerability in the Oracle Java SE, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component:…5.3 0.0349 None reported
Routine CVE-2022-21299 Microsoft Build of OpenJDK with Hotspot 11: Uncontrolled Resource Consumption5.3 0.0346 None reported
Routine CVE-2022-21294 Microsoft Build of OpenJDK with Hotspot 11: Allocation of Resources Without Limits or Throttling5.3 0.0335 None reported
Routine CVE-2022-21366 Microsoft Build of OpenJDK with Hotspot 11: Uncontrolled Resource Consumption5.3 0.0322 None reported
Routine CVE-2022-21277 Microsoft Build of OpenJDK with Hotspot 11: Uncontrolled Resource Consumption5.3 0.0309 None reported
Routine CVE-2022-21291 Microsoft Build of OpenJDK with Hotspot 11: Improper Access Control5.3 0.0290 None reported
Routine CVE-2022-21282 Microsoft Build of OpenJDK with Hotspot 11: Improper Restriction of XML External Entity Reference5.3 0.0288 None reported
Routine CVE-2022-21296 Microsoft Build of OpenJDK with Hotspot 11: Exposure of Sensitive Information to an Unauthorized Actor5.3 0.0283 None reported
Routine CVE-2022-21305 Microsoft Build of OpenJDK with Hotspot 11: Improper Access Control5.3 0.0276 None reported
Showing 1 to 15 of 15 1

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.