Tri

Name of the Vulnerable Software and Affected Versions: QNAP QTS versions prior to 5.2.1.2930 build 20241025 QNAP QuTS hero versions prior to h5.2.1.2929 build 20241025 Description: A use of externally-controlled format string vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow remote attackers to obtain secret data or modify memory. Recommendations: For QNAP QTS versions prior to 5.2.1.2930 build 20241025, update to QTS 5.2.1.2930 build 20241025 or later. For QNAP QuTS hero versions prior to h5.2.1.2929 build 20241025, update to QuTS hero h5.2.1.2929 build 20241025 or later.

Name of the Vulnerable Software and Affected Versions: QNAP QTS versions prior to 5.2.1.2930 build 20241025 QNAP QuTS hero versions prior to h5.2.1.2929 build 20241025 Description: A use of externally-controlled format string vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow remote attackers who have gained administrator access to obtain secret data or modify memory. Recommendations: For QNAP QTS versions prior to 5.2.1.2930 build 20241025, update to QTS 5.2.1.2930 build 20241025 or later. For QNAP QuTS hero versions prior to h5.2.1.2929 build 20241025, update to QuTS hero h5.2.1.2929 build 20241025 or later.

A command injection vulnerability has been reported to affect License Center. If exploited, the vulnerability could allow remote attackers to execute arbitrary commands. This issue is related to the failure to neutralize special elements used in operating system commands.

An improper authentication vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow remote attackers to compromise the security of the system.

This issue allows network-adjacent attackers to execute arbitrary code on affected installations of Sonos Era 100 smart speakers. Authentication is not required to exploit this issue. The specific flaw exists within the handling of SMB2 messages, resulting from the lack of validating the existence of an object prior to performing operations on the object. An attacker can leverage this issue to execute code in the context of root.