Skip to content

Commit 38810bd

Browse files
authored
Merge pull request #53584 from libander/RHDEVDOCS-4752
RHDEVDOCS-4752 - Logging 5.4.9 Release Notes
2 parents 9499b69 + a677211 commit 38810bd

File tree

2 files changed

+87
-0
lines changed

2 files changed

+87
-0
lines changed

logging/cluster-logging-release-notes.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,8 @@ This release includes link:https://access.redhat.com/errata/RHSA-2022:6344[OpenS
5050

5151
include::modules/cluster-logging-rn-5.5.adoc[leveloffset=+1]
5252

53+
include::modules/cluster-logging-rn-5.4.9.adoc[leveloffset=+1]
54+
5355
include::modules/cluster-logging-rn-5.4.8.adoc[leveloffset=+1]
5456

5557
//include::modules/cluster-logging-rn-5.4.7.adoc[leveloffset=+1]

modules/cluster-logging-rn-5.4.9.adoc

Lines changed: 85 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,85 @@
1+
//module included in cluster-logging-release-notes.adoc
2+
:_content-type: REFERENCE
3+
[id="cluster-logging-release-notes-5-4-9_{context}"]
4+
= Logging 5.4.9
5+
This release includes link:https://access.redhat.com/errata/RHBA-2022:8780[OpenShift Logging Bug Fix Release 5.4.9].
6+
7+
[id="openshift-logging-5-4-9-bug-fixes"]
8+
== Bug fixes
9+
* Before this update, the Fluentd collector would warn of unused configuration parameters. This update removes those configuration parameters and their warning messages. (link:https://issues.redhat.com/browse/LOG-3074[LOG-3074])
10+
11+
* Before this update, Kibana had a fixed `24h` OAuth cookie expiration time, which resulted in 401 errors in Kibana whenever the `accessTokenInactivityTimeout` field was set to a value lower than `24h`. With this update, Kibana's OAuth cookie expiration time synchronizes to the `accessTokenInactivityTimeout`, with a default value of `24h`. (link:https://issues.redhat.com/browse/LOG-3306[LOG-3306])
12+
13+
[id="openshift-logging-5-4-9-CVEs"]
14+
== CVEs
15+
* link:https://access.redhat.com/security/cve/CVE-2016-3709[CVE-2016-3709]
16+
* link:https://access.redhat.com/security/cve/CVE-2020-35525[CVE-2020-35525]
17+
* link:https://access.redhat.com/security/cve/CVE-2020-35527[CVE-2020-35527]
18+
* link:https://access.redhat.com/security/cve/CVE-2020-36516[CVE-2020-36516]
19+
* link:https://access.redhat.com/security/cve/CVE-2020-36558[CVE-2020-36558]
20+
* link:https://access.redhat.com/security/cve/CVE-2021-3640[CVE-2021-3640]
21+
* link:https://access.redhat.com/security/cve/CVE-2021-30002[CVE-2021-30002]
22+
* link:https://access.redhat.com/security/cve/CVE-2022-0168[CVE-2022-0168]
23+
* link:https://access.redhat.com/security/cve/CVE-2022-0561[CVE-2022-0561]
24+
* link:https://access.redhat.com/security/cve/CVE-2022-0562[CVE-2022-0562]
25+
* link:https://access.redhat.com/security/cve/CVE-2022-0617[CVE-2022-0617]
26+
* link:https://access.redhat.com/security/cve/CVE-2022-0854[CVE-2022-0854]
27+
* link:https://access.redhat.com/security/cve/CVE-2022-0865[CVE-2022-0865]
28+
* link:https://access.redhat.com/security/cve/CVE-2022-0891[CVE-2022-0891]
29+
* link:https://access.redhat.com/security/cve/CVE-2022-0908[CVE-2022-0908]
30+
* link:https://access.redhat.com/security/cve/CVE-2022-0909[CVE-2022-0909]
31+
* link:https://access.redhat.com/security/cve/CVE-2022-0924[CVE-2022-0924]
32+
* link:https://access.redhat.com/security/cve/CVE-2022-1016[CVE-2022-1016]
33+
* link:https://access.redhat.com/security/cve/CVE-2022-1048[CVE-2022-1048]
34+
* link:https://access.redhat.com/security/cve/CVE-2022-1055[CVE-2022-1055]
35+
* link:https://access.redhat.com/security/cve/CVE-2022-1184[CVE-2022-1184]
36+
* link:https://access.redhat.com/security/cve/CVE-2022-1292[CVE-2022-1292]
37+
* link:https://access.redhat.com/security/cve/CVE-2022-1304[CVE-2022-1304]
38+
* link:https://access.redhat.com/security/cve/CVE-2022-1355[CVE-2022-1355]
39+
* link:https://access.redhat.com/security/cve/CVE-2022-1586[CVE-2022-1586]
40+
* link:https://access.redhat.com/security/cve/CVE-2022-1785[CVE-2022-1785]
41+
* link:https://access.redhat.com/security/cve/CVE-2022-1852[CVE-2022-1852]
42+
* link:https://access.redhat.com/security/cve/CVE-2022-1897[CVE-2022-1897]
43+
* link:https://access.redhat.com/security/cve/CVE-2022-1927[CVE-2022-1927]
44+
* link:https://access.redhat.com/security/cve/CVE-2022-2068[CVE-2022-2068]
45+
* link:https://access.redhat.com/security/cve/CVE-2022-2078[CVE-2022-2078]
46+
* link:https://access.redhat.com/security/cve/CVE-2022-2097[CVE-2022-2097]
47+
* link:https://access.redhat.com/security/cve/CVE-2022-2509[CVE-2022-2509]
48+
* link:https://access.redhat.com/security/cve/CVE-2022-2586[CVE-2022-2586]
49+
* link:https://access.redhat.com/security/cve/CVE-2022-2639[CVE-2022-2639]
50+
* link:https://access.redhat.com/security/cve/CVE-2022-2938[CVE-2022-2938]
51+
* link:https://access.redhat.com/security/cve/CVE-2022-3515[CVE-2022-3515]
52+
* link:https://access.redhat.com/security/cve/CVE-2022-20368[CVE-2022-20368]
53+
* link:https://access.redhat.com/security/cve/CVE-2022-21499[CVE-2022-21499]
54+
* link:https://access.redhat.com/security/cve/CVE-2022-21618[CVE-2022-21618]
55+
* link:https://access.redhat.com/security/cve/CVE-2022-21619[CVE-2022-21619]
56+
* link:https://access.redhat.com/security/cve/CVE-2022-21624[CVE-2022-21624]
57+
* link:https://access.redhat.com/security/cve/CVE-2022-21626[CVE-2022-21626]
58+
* link:https://access.redhat.com/security/cve/CVE-2022-21628[CVE-2022-21628]
59+
* link:https://access.redhat.com/security/cve/CVE-2022-22624[CVE-2022-22624]
60+
* link:https://access.redhat.com/security/cve/CVE-2022-22628[CVE-2022-22628]
61+
* link:https://access.redhat.com/security/cve/CVE-2022-22629[CVE-2022-22629]
62+
* link:https://access.redhat.com/security/cve/CVE-2022-22662[CVE-2022-22662]
63+
* link:https://access.redhat.com/security/cve/CVE-2022-22844[CVE-2022-22844]
64+
* link:https://access.redhat.com/security/cve/CVE-2022-23960[CVE-2022-23960]
65+
* link:https://access.redhat.com/security/cve/CVE-2022-24448[CVE-2022-24448]
66+
* link:https://access.redhat.com/security/cve/CVE-2022-25255[CVE-2022-25255]
67+
* link:https://access.redhat.com/security/cve/CVE-2022-26373[CVE-2022-26373]
68+
* link:https://access.redhat.com/security/cve/CVE-2022-26700[CVE-2022-26700]
69+
* link:https://access.redhat.com/security/cve/CVE-2022-26709[CVE-2022-26709]
70+
* link:https://access.redhat.com/security/cve/CVE-2022-26710[CVE-2022-26710]
71+
* link:https://access.redhat.com/security/cve/CVE-2022-26716[CVE-2022-26716]
72+
* link:https://access.redhat.com/security/cve/CVE-2022-26717[CVE-2022-26717]
73+
* link:https://access.redhat.com/security/cve/CVE-2022-26719[CVE-2022-26719]
74+
* link:https://access.redhat.com/security/cve/CVE-2022-27404[CVE-2022-27404]
75+
* link:https://access.redhat.com/security/cve/CVE-2022-27405[CVE-2022-27405]
76+
* link:https://access.redhat.com/security/cve/CVE-2022-27406[CVE-2022-27406]
77+
* link:https://access.redhat.com/security/cve/CVE-2022-27950[CVE-2022-27950]
78+
* link:https://access.redhat.com/security/cve/CVE-2022-28390[CVE-2022-28390]
79+
* link:https://access.redhat.com/security/cve/CVE-2022-28893[CVE-2022-28893]
80+
* link:https://access.redhat.com/security/cve/CVE-2022-29581[CVE-2022-29581]
81+
* link:https://access.redhat.com/security/cve/CVE-2022-30293[CVE-2022-30293]
82+
* link:https://access.redhat.com/security/cve/CVE-2022-34903[CVE-2022-34903]
83+
* link:https://access.redhat.com/security/cve/CVE-2022-36946[CVE-2022-36946]
84+
* link:https://access.redhat.com/security/cve/CVE-2022-37434[CVE-2022-37434]
85+
* link:https://access.redhat.com/security/cve/CVE-2022-39399[CVE-2022-39399]

0 commit comments

Comments
 (0)