|
| 1 | +:_content-type: REFERENCE |
| 2 | +[id="cluster-logging-release-notes-5-4-2"] |
| 3 | += Logging 5.4.2 |
| 4 | +This release includes link:https://access.redhat.com/errata/RHBA-2022:4874[RHBA-2022:4874-OpenShift Logging Bug Fix Release 5.4.2] |
| 5 | + |
| 6 | +[id="openshift-logging-5-4-2-bug-fixes"] |
| 7 | +== Bug fixes |
| 8 | +* Before this update, editing the Collector configuration using `oc edit` was difficult because it had inconsistent use of white-space. This change introduces logic to normalize and format the configuration prior to any updates by the Operator so that it is easy to edit using `oc edit`. (link:https://issues.redhat.com/browse/LOG-2319[LOG-2319]) |
| 9 | + |
| 10 | +* Before this update, the `FluentdNodeDown` alert could not provide instance labels in the message section appropriately. This update resolves the issue by fixing the alert rule to provide instance labels in cases of partial instance failures. (link:https://issues.redhat.com/browse/LOG-2607[LOG-2607]) |
| 11 | + |
| 12 | +* Before this update, several log levels, such as`critical`, that were documented as supported by the product were not. This update fixes the discrepancy so the documented log levels are now supported by the product. (link:https://issues.redhat.com/browse/LOG-2033[LOG-2033]) |
| 13 | + |
| 14 | +[id="openshift-logging-5-4-2-CVEs"] |
| 15 | +== CVEs |
| 16 | +.Click to expand CVEs |
| 17 | +[%collapsible] |
| 18 | +==== |
| 19 | +* link:https://access.redhat.com/security/cve/CVE-2018-25032[CVE-2018-25032] |
| 20 | +* link:https://access.redhat.com/security/cve/CVE-2020-0404[CVE-2020-0404] |
| 21 | +* link:https://access.redhat.com/security/cve/CVE-2020-4788[CVE-2020-4788] |
| 22 | +* link:https://access.redhat.com/security/cve/CVE-2020-13974[CVE-2020-13974] |
| 23 | +* link:https://access.redhat.com/security/cve/CVE-2020-19131[CVE-2020-19131] |
| 24 | +* link:https://access.redhat.com/security/cve/CVE-2020-27820[CVE-2020-27820] |
| 25 | +* link:https://access.redhat.com/security/cve/CVE-2021-0941[CVE-2021-0941] |
| 26 | +* link:https://access.redhat.com/security/cve/CVE-2021-3612[CVE-2021-3612] |
| 27 | +* link:https://access.redhat.com/security/cve/CVE-2021-3634[CVE-2021-3634] |
| 28 | +* link:https://access.redhat.com/security/cve/CVE-2021-3669[CVE-2021-3669] |
| 29 | +* link:https://access.redhat.com/security/cve/CVE-2021-3737[CVE-2021-3737] |
| 30 | +* link:https://access.redhat.com/security/cve/CVE-2021-3743[CVE-2021-3743] |
| 31 | +* link:https://access.redhat.com/security/cve/CVE-2021-3744[CVE-2021-3744] |
| 32 | +* link:https://access.redhat.com/security/cve/CVE-2021-3752[CVE-2021-3752] |
| 33 | +* link:https://access.redhat.com/security/cve/CVE-2021-3759[CVE-2021-3759] |
| 34 | +* link:https://access.redhat.com/security/cve/CVE-2021-3764[CVE-2021-3764] |
| 35 | +* link:https://access.redhat.com/security/cve/CVE-2021-3772[CVE-2021-3772] |
| 36 | +* link:https://access.redhat.com/security/cve/CVE-2021-3773[CVE-2021-3773] |
| 37 | +* link:https://access.redhat.com/security/cve/CVE-2021-4002[CVE-2021-4002] |
| 38 | +* link:https://access.redhat.com/security/cve/CVE-2021-4037[CVE-2021-4037] |
| 39 | +* link:https://access.redhat.com/security/cve/CVE-2021-4083[CVE-2021-4083] |
| 40 | +* link:https://access.redhat.com/security/cve/CVE-2021-4157[CVE-2021-4157] |
| 41 | +* link:https://access.redhat.com/security/cve/CVE-2021-4189[CVE-2021-4189] |
| 42 | +* link:https://access.redhat.com/security/cve/CVE-2021-4197[CVE-2021-4197] |
| 43 | +* link:https://access.redhat.com/security/cve/CVE-2021-4203[CVE-2021-4203] |
| 44 | +* link:https://access.redhat.com/security/cve/CVE-2021-20322[CVE-2021-20322] |
| 45 | +* link:https://access.redhat.com/security/cve/CVE-2021-21781[CVE-2021-21781] |
| 46 | +* link:https://access.redhat.com/security/cve/CVE-2021-23222[CVE-2021-23222] |
| 47 | +* link:https://access.redhat.com/security/cve/CVE-2021-26401[CVE-2021-26401] |
| 48 | +* link:https://access.redhat.com/security/cve/CVE-2021-29154[CVE-2021-29154] |
| 49 | +* link:https://access.redhat.com/security/cve/CVE-2021-37159[CVE-2021-37159] |
| 50 | +* link:https://access.redhat.com/security/cve/CVE-2021-41617[CVE-2021-41617] |
| 51 | +* link:https://access.redhat.com/security/cve/CVE-2021-41864[CVE-2021-41864] |
| 52 | +* link:https://access.redhat.com/security/cve/CVE-2021-42739[CVE-2021-42739] |
| 53 | +* link:https://access.redhat.com/security/cve/CVE-2021-43056[CVE-2021-43056] |
| 54 | +* link:https://access.redhat.com/security/cve/CVE-2021-43389[CVE-2021-43389] |
| 55 | +* link:https://access.redhat.com/security/cve/CVE-2021-43976[CVE-2021-43976] |
| 56 | +* link:https://access.redhat.com/security/cve/CVE-2021-44733[CVE-2021-44733] |
| 57 | +* link:https://access.redhat.com/security/cve/CVE-2021-45485[CVE-2021-45485] |
| 58 | +* link:https://access.redhat.com/security/cve/CVE-2021-45486[CVE-2021-45486] |
| 59 | +* link:https://access.redhat.com/security/cve/CVE-2022-0001[CVE-2022-0001] |
| 60 | +* link:https://access.redhat.com/security/cve/CVE-2022-0002[CVE-2022-0002] |
| 61 | +* link:https://access.redhat.com/security/cve/CVE-2022-0286[CVE-2022-0286] |
| 62 | +* link:https://access.redhat.com/security/cve/CVE-2022-0322[CVE-2022-0322] |
| 63 | +* link:https://access.redhat.com/security/cve/CVE-2022-1011[CVE-2022-1011] |
| 64 | +* link:https://access.redhat.com/security/cve/CVE-2022-1271[CVE-2022-1271] |
| 65 | +==== |
0 commit comments