ASA-202101-44 - log back

ASA-202101-44 edited at 29 Jan 2021 19:32:40
Workaround
- The issue can be mitigated by disabling all custom integrations. This is achieved by renaming the custom_components folder inside the Home Assistant configuration folder to something else and restarting Home Assistant.
+ The issue can be mitigated by disabling all custom integrations. This
+ is achieved by renaming the custom_components folder inside the Home
+ Assistant configuration folder to something else and restarting Home
+ Assistant.
ASA-202101-44 edited at 29 Jan 2021 16:38:37
Impact
- Some plugins could allow malicious users to read sensitive information.
+ Some integrations could allow malicious users to read sensitive information.
ASA-202101-44 edited at 29 Jan 2021 16:38:24
Workaround
+ The issue can be mitigated by disabling all custom integrations. This is achieved by renaming the custom_components folder inside the Home Assistant configuration folder to something else and restarting Home Assistant.
ASA-202101-44 edited at 29 Jan 2021 16:33:52
Impact
+ Some plugins could allow malicious users to read sensitive information.
ASA-202101-44 created at 29 Jan 2021 16:26:36