A critical denial of service vulnerability in the MERCURY MIPC252W camera allows unauthenticated remote attackers to force device reboots by sending malformed RTSP requests.

The flaw exists in the RTSP service handler, which fails to validate the Transport header field during a SETUP request. An unauthenticated attacker can trigger a null pointer dereference by providing a specifically crafted header, resulting in an immediate service crash and system reboot.

Successful exploitation results in the persistent denial of service for the affected surveillance hardware. Because the vulnerability allows for remote, unauthenticated triggers, it poses a significant risk to the physical security monitoring capabilities of any organization relying on these devices. With a CVSS score of 7.5, the high availability impact justifies immediate attention to prevent operational disruption.

Immediate Action: Given that no official patch is currently identified, isolate the affected devices from public-facing networks and restrict access to the RTSP port (554) to trusted management subnets.

Proactive Monitoring: Monitor network traffic for anomalous RTSP SETUP requests and review device logs for frequent, unexplained system reboots.

Compensating Controls: Deploy a network-level firewall or intrusion prevention system to filter or block malformed RTSP traffic targeting the device.

Public Exploit Available: Yes, a published proof-of-concept exists, as documented in the technical research write-up provided in the CVE references.

Organizations utilizing the MERCURY MIPC252W should treat this vulnerability as a high-priority risk to operational continuity. Since a public proof-of-concept is available, the barrier to entry for an attacker is minimal. Until a manufacturer-supplied firmware update is released, strict network segmentation is the most effective method to prevent unauthorized reboots and maintain service availability.