Nguyen Hoang Thach

**Name of the Vulnerable Software and Affected Versions** Google Chrome versions prior to 129.0.6668.100 **Description** The issue is related to a type confusion in the V8 component of Google Chrome, which could allow a remote attacker to potentially exploit heap corruption via a crafted HTML page. The severity of this issue is considered high. **Recommendations** For Google Chrome versions prior to 129.0.6668.100, upgrade to a patched version to resolve the issue. As a temporary workaround, consider avoiding the use of potentially vulnerable HTML pages until the update is applied.

**Name of the Vulnerable Software and Affected Versions** Sonos One Speaker version 70.3-35220 **Description** This issue allows network-adjacent attackers to disclose sensitive information on affected installations. Authentication is not required to exploit this issue. The specific flaw exists within the "msprox" endpoint. The issue results from the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated buffer. An attacker can leverage this in conjunction with other issues to execute arbitrary code in the context of root. **Recommendations** For Sonos One Speaker version 70.3-35220, as a temporary workaround, consider restricting access to the "msprox" endpoint until a patch is available. At the moment, there is no information about a newer version that contains a fix for this issue.

**Name of the Vulnerable Software and Affected Versions** TP-LINK TL-WR841N (affected versions not specified) **Description** This issue allows remote attackers to execute arbitrary code on affected installations. Authentication is not required to exploit this issue. The flaw exists within the web service, which listens on TCP port 80 by default. When parsing the `Host` request header, the process does not properly validate the length of user-supplied data prior to copying it to a fixed-length static buffer. An attacker can leverage this issue to execute code in the context of the admin user. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this issue.