A critical stack-based buffer overflow in the Linksys E1700 router poses a severe risk of remote code execution and persistent service disruption.

The vulnerability exists in the QoSSetup function of the /goform/QoSSetup endpoint, where the ack_policy argument is copied into a stack buffer without proper length validation. An authenticated attacker can trigger this memory corruption to overwrite the function return address and achieve remote code execution.

This vulnerability carries a CVSS score of 8.8, reflecting its high potential for system compromise. Successful exploitation results in complete loss of router availability and the ability for unauthorized actors to execute arbitrary code within the device environment. This poses a significant threat to network integrity, potentially allowing lateral movement into internal segments or the interception of sensitive traffic.

Immediate Action: As the vendor has not provided a patch for this specific firmware version, users should restrict administrative access to the router and disable the QoS feature if it is not required for network operations.

Proactive Monitoring: Security teams should monitor network traffic for anomalous POST requests directed at /goform/QoSSetup and review system logs for recurring service crashes or unexpected reboots.

Compensating Controls: Implement an access control list (ACL) to restrict management interface access to trusted internal IP addresses only, and deploy a Web Application Firewall (WAF) or equivalent inspection tool to filter malicious payloads targeting the ack_policy parameter.

Public Exploit Available: Yes, a proof-of-concept is documented in the researcher's technical write-up provided in the references.

Given the lack of a vendor-supplied security update, this vulnerability presents a persistent risk to the affected hardware. Administrators are urged to isolate the management interface from the public internet immediately and monitor for signs of exploitation. If the device cannot be secured via configuration changes, consider retiring the affected hardware in favor of supported alternatives.