[DOCS] Add security update to 8.11.1 RNs (#171228)

Co-authored-by: Amy Jonsson <amy.jonsson@elastic.co>
This commit is contained in:
James Rodewig 2023-11-14 16:29:35 -05:00 committed by GitHub
parent 6ebad69948
commit cb40acc7ba
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -58,7 +58,23 @@ Review important information about the {kib} 8.x releases.
[[release-notes-8.11.1]]
== {kib} 8.11.1
The 8.11.1 release includes the following bug fixes.
For information about the {kib} 8.11.1 release, review the following information.
[float]
[[security-update-v8.11.1]]
=== Security updates
* An issue was discovered by Elastic whereby sensitive information is recorded
in {kib} logs in the event of an error. The error message recorded in the log
may contain account credentials for the `kibana_system` user, API Keys, and
credentials of {kib} end users.
+
The issue impacts {kib} versions before 7.17.15 and {kib} versions on or after
8.0.0 and before 8.11.1. The issue is resolved in {kib} 8.11.1 and {kib} 7.17.15.
+
For more information, see our related
https://discuss.elastic.co/t/8-11-1-7-17-15-security-update-esa-2023-25/347149[security
announcement].
[float]
[[fixes-v8.11.1]]
@ -799,10 +815,10 @@ For information about the {kib} 8.9.0 release, review the following information.
[%collapsible]
====
*Details* +
Changes to Lens visualizations do not appear in the saved object.
Changes to Lens visualizations do not appear in the saved object.
*Impact* +
When you remove fields from Lens visualizations, then save your changes, the removed fields continue to appear in the Lens visualization saved objects.
When you remove fields from Lens visualizations, then save your changes, the removed fields continue to appear in the Lens visualization saved objects.
For example, when you remove runtime fields from a Lens visualization and {kib}, then inspect the Lens visualization saved object, the runtime fields continue to appear and an error message appears.
*Workaround* +