Part of the Cure53 security audit of Home Assistant.
The audit team noted that the Home Assistant server does not set any HTTP security headers, including the X-Frame-Options header, which specifies whether the web page is allowed to be framed. The omission of this and correlating headers facilitates covert clickjacking attacks and alternative exploit opportunities, such as the vector described in this security advisory.
This fault incurs major risk, considering the ability to trick users into installing an external and malicious add-on with minimal user interaction, which would enable Remote Code Execution (RCE) within the Home Assistant application.
To mitigate this issue, Cure53 strongly suggests setting the XFO header to prevent clickjacking and other attack strategies when a web page is framable. For optimal configuration, the developer team should set the header’s value to either SAMEORIGIN or DENY.
Part of the Cure53 security audit of Home Assistant.
The audit team noted that the Home Assistant server does not set any HTTP security headers, including the
X-Frame-Optionsheader, which specifies whether the web page is allowed to be framed. The omission of this and correlating headers facilitates covert clickjacking attacks and alternative exploit opportunities, such as the vector described in this security advisory.This fault incurs major risk, considering the ability to trick users into installing an external and malicious add-on with minimal user interaction, which would enable Remote Code Execution (RCE) within the Home Assistant application.
To mitigate this issue, Cure53 strongly suggests setting the XFO header to prevent clickjacking and other attack strategies when a web page is framable. For optimal configuration, the developer team should set the header’s value to either SAMEORIGIN or DENY.