|
| 1 | +// Module included in the following assemblies: |
| 2 | +// |
| 3 | +// logging-5-7-release-notes.adoc |
| 4 | +// cluster-logging-release-notes.adoc |
| 5 | +:_content-type: REFERENCE |
| 6 | +[id="logging-release-notes-5-5-11_{context}"] |
| 7 | += Logging 5.5.11 |
| 8 | +This release includes link:https://access.redhat.com/errata/RHBA-2023:3196[OpenShift Logging Bug Fix Release 5.5.11]. |
| 9 | + |
| 10 | +[id="logging-5-5-11-bug-fixes_{context}"] |
| 11 | +== Bug fixes |
| 12 | +* Before this update, a time range could not be selected in the {Product-Title} web console by clicking and dragging over the logs histogram. With this update, clicking and dragging can be used to successfully select a time range. (link:https://issues.redhat.com/browse/LOG-4102[LOG-4102]) |
| 13 | + |
| 14 | +* Before this update, clicking on the *Show Resources* link in the {Product-Title} web console did not produce any effect. With this update, the issue is resolved by fixing the functionality of the *Show Resources* link to toggle the display of resources for each log entry. (link:https://issues.redhat.com/browse/LOG-4117[LOG-4117]) |
| 15 | + |
| 16 | +[id="logging-5-5-11-CVEs_{context}"] |
| 17 | +== CVEs |
| 18 | +* link:https://access.redhat.com/security/cve/CVE-2021-26341[CVE-2021-26341] |
| 19 | +* link:https://access.redhat.com/security/cve/CVE-2021-33655[CVE-2021-33655] |
| 20 | +* link:https://access.redhat.com/security/cve/CVE-2021-33656[CVE-2021-33656] |
| 21 | +* link:https://access.redhat.com/security/cve/CVE-2022-1462[CVE-2022-1462] |
| 22 | +* link:https://access.redhat.com/security/cve/CVE-2022-1679[CVE-2022-1679] |
| 23 | +* link:https://access.redhat.com/security/cve/CVE-2022-1789[CVE-2022-1789] |
| 24 | +* link:https://access.redhat.com/security/cve/CVE-2022-2196[CVE-2022-2196] |
| 25 | +* link:https://access.redhat.com/security/cve/CVE-2022-2663[CVE-2022-2663] |
| 26 | +* link:https://access.redhat.com/security/cve/CVE-2022-2795[CVE-2022-2795] |
| 27 | +* link:https://access.redhat.com/security/cve/CVE-2022-3028[CVE-2022-3028] |
| 28 | +* link:https://access.redhat.com/security/cve/CVE-2022-3239[CVE-2022-3239] |
| 29 | +* link:https://access.redhat.com/security/cve/CVE-2022-3522[CVE-2022-3522] |
| 30 | +* link:https://access.redhat.com/security/cve/CVE-2022-3524[CVE-2022-3524] |
| 31 | +* link:https://access.redhat.com/security/cve/CVE-2022-3564[CVE-2022-3564] |
| 32 | +* link:https://access.redhat.com/security/cve/CVE-2022-3566[CVE-2022-3566] |
| 33 | +* link:https://access.redhat.com/security/cve/CVE-2022-3567[CVE-2022-3567] |
| 34 | +* link:https://access.redhat.com/security/cve/CVE-2022-3619[CVE-2022-3619] |
| 35 | +* link:https://access.redhat.com/security/cve/CVE-2022-3623[CVE-2022-3623] |
| 36 | +* link:https://access.redhat.com/security/cve/CVE-2022-3625[CVE-2022-3625] |
| 37 | +* link:https://access.redhat.com/security/cve/CVE-2022-3627[CVE-2022-3627] |
| 38 | +* link:https://access.redhat.com/security/cve/CVE-2022-3628[CVE-2022-3628] |
| 39 | +* link:https://access.redhat.com/security/cve/CVE-2022-3707[CVE-2022-3707] |
| 40 | +* link:https://access.redhat.com/security/cve/CVE-2022-3970[CVE-2022-3970] |
| 41 | +* link:https://access.redhat.com/security/cve/CVE-2022-4129[CVE-2022-4129] |
| 42 | +* link:https://access.redhat.com/security/cve/CVE-2022-20141[CVE-2022-20141] |
| 43 | +* link:https://access.redhat.com/security/cve/CVE-2022-24765[CVE-2022-24765] |
| 44 | +* link:https://access.redhat.com/security/cve/CVE-2022-25265[CVE-2022-25265] |
| 45 | +* link:https://access.redhat.com/security/cve/CVE-2022-29187[CVE-2022-29187] |
| 46 | +* link:https://access.redhat.com/security/cve/CVE-2022-30594[CVE-2022-30594] |
| 47 | +* link:https://access.redhat.com/security/cve/CVE-2022-36227[CVE-2022-36227] |
| 48 | +* link:https://access.redhat.com/security/cve/CVE-2022-39188[CVE-2022-39188] |
| 49 | +* link:https://access.redhat.com/security/cve/CVE-2022-39189[CVE-2022-39189] |
| 50 | +* link:https://access.redhat.com/security/cve/CVE-2022-39253[CVE-2022-39253] |
| 51 | +* link:https://access.redhat.com/security/cve/CVE-2022-39260[CVE-2022-39260] |
| 52 | +* link:https://access.redhat.com/security/cve/CVE-2022-41218[CVE-2022-41218] |
| 53 | +* link:https://access.redhat.com/security/cve/CVE-2022-41674[CVE-2022-41674] |
| 54 | +* link:https://access.redhat.com/security/cve/CVE-2022-42703[CVE-2022-42703] |
| 55 | +* link:https://access.redhat.com/security/cve/CVE-2022-42720[CVE-2022-42720] |
| 56 | +* link:https://access.redhat.com/security/cve/CVE-2022-42721[CVE-2022-42721] |
| 57 | +* link:https://access.redhat.com/security/cve/CVE-2022-42722[CVE-2022-42722] |
| 58 | +* link:https://access.redhat.com/security/cve/CVE-2022-43750[CVE-2022-43750] |
| 59 | +* link:https://access.redhat.com/security/cve/CVE-2022-47929[CVE-2022-47929] |
| 60 | +* link:https://access.redhat.com/security/cve/CVE-2023-0394[CVE-2023-0394] |
| 61 | +* link:https://access.redhat.com/security/cve/CVE-2023-0461[CVE-2023-0461] |
| 62 | +* link:https://access.redhat.com/security/cve/CVE-2023-1195[CVE-2023-1195] |
| 63 | +* link:https://access.redhat.com/security/cve/CVE-2023-1582[CVE-2023-1582] |
| 64 | +* link:https://access.redhat.com/security/cve/CVE-2023-2491[CVE-2023-2491] |
| 65 | +* link:https://access.redhat.com/security/cve/CVE-2023-23454[CVE-2023-23454] |
| 66 | +* link:https://access.redhat.com/security/cve/CVE-2023-27535[CVE-2023-27535] |
0 commit comments