Improper session invalidation in the component /banker/change-password
Description
Improper session invalidation in the component /banker/change-password
Remediation
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Executive Summary:
A critical vulnerability has been identified in multiple Russound products, including the MBX-PRE-D67F firmware. This flaw allows an unauthenticated attacker to remotely execute arbitrary commands with the highest system privileges by sending a crafted request. Successful exploitation could lead to a complete compromise of the affected device, enabling attackers to pivot into the internal network, steal data, or disrupt operations.
Vulnerability Details
CVE-ID: CVE-2025-50475
Affected Software: Russound Multiple Products
Affected Versions: Russound MBX-PRE-D67F firmware version 3.1.6. Other products may be affected; see vendor advisory for a complete list.
Vulnerability: The vulnerability is an unauthenticated OS command injection flaw. An attacker can send a specially crafted network request to a function that modifies the device's hostname. The system fails to properly sanitize the input provided for the new hostname, allowing the attacker to inject and execute arbitrary operating system commands. These commands are executed with root privileges, giving the attacker complete control over the underlying operating system of the device.
Business Impact
This vulnerability is rated as critical with a CVSS score of 9.8, reflecting the extreme risk it poses to the organization. An attacker requires no authentication and can exploit this vulnerability remotely over the network. A successful attack would result in a full system compromise, allowing the threat actor to install persistent backdoors, exfiltrate sensitive data passing through the device, use the device as a launchpad for further attacks against the internal network, or deploy malware such as ransomware. The complete control gained by an attacker could lead to significant operational disruption, data breaches, and reputational damage.
Remediation Plan
Immediate Action: Immediately update all affected Russound products to the latest firmware version as recommended by the vendor. Prioritize patching for devices that are accessible from the internet. After patching, review system and access logs for any signs of compromise that may have occurred before the update was applied.
Proactive Monitoring: Implement enhanced monitoring of network traffic to and from affected devices. Specifically, look for unusual requests to the device's management interface, especially those related to hostname changes. Monitor for unexpected outbound connections from the devices to unknown destinations and review system logs for evidence of suspicious command execution or unexpected processes.
Compensating Controls: If immediate patching is not feasible, implement compensating controls to reduce the risk of exploitation. Isolate the affected devices onto a segmented network VLAN with strict firewall rules, restricting all access to the management interface except from a small set of trusted administrative IP addresses. Deploy an Intrusion Prevention System (IPS) with signatures capable of detecting and blocking OS command injection attempts.
Exploitation Status
Public Exploit Available: False
Analyst Notes: As of Jul 31, 2025, there are no known public exploits or active exploitation campaigns targeting this vulnerability. The vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog. However, given the critical severity and simplicity of exploitation, it is highly likely that threat actors will develop and release exploit code in the near future.
Analyst Recommendation
Due to the critical CVSS score of 9.8 and the potential for a complete, unauthenticated remote system compromise, this vulnerability requires immediate attention. We strongly recommend that all affected Russound devices be patched immediately. If patching cannot be performed right away, the compensating controls outlined above, particularly network segmentation and access restriction, must be implemented as a matter of urgency. Organizations should operate under the assumption that an exploit will become publicly available and treat this as a critical, time-sensitive priority.