CVE-2026-93738

9.9

Totolink · A3002MU

A buffer overflow vulnerability in the Totolink A3002MU router allows remote attackers to cause a denial of service via a crafted webpage parameter in the formSchedule function.

Executive summary

A critical buffer overflow vulnerability in the Totolink A3002MU router allows a remote attacker to crash the device, necessitating immediate network isolation.

Vulnerability

This is a memory corruption vulnerability (CWE-120) located in the /boafrm/formSchedule endpoint of the Boa web server. By sending a specially crafted HTTP POST request with an overlong webpage parameter, an authenticated attacker can overflow a fixed-size buffer, leading to a crash of the web service.

Business impact

The exploitation of this vulnerability results in a denial of service, rendering the device management interface unresponsive. Given the CVSS score of 9.9, this represents a severe threat to network availability and device management, as the router is a critical gateway component. Organizations relying on this hardware may face significant operational downtime and loss of network control.

Remediation

Immediate Action: As no vendor patch is currently confirmed, administrators should restrict access to the management interface of the A3002MU router to trusted internal management networks only.

Proactive Monitoring: Monitor device logs for recurring web server crashes or failed login attempts targeting the /boafrm/formSchedule endpoint.

Compensating Controls: Deploy a Web Application Firewall or an intrusion prevention system to filter HTTP POST requests containing abnormally long strings in the webpage parameter.

Exploitation status

Public Exploit Available: Yes, a published proof-of-concept exists and is attributed to the technical write-up referenced in the CVE record.

Analyst recommendation

This vulnerability presents a high risk to infrastructure stability due to the availability of proof-of-concept code. Administrators must prioritize isolating the affected device from public-facing exposure and monitor for vendor updates, as the lack of a formal patch requires strict perimeter defense until a firmware update is released.

More Totolink CVEs all →

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief critical section

Sources

Originally found and disclosed by sunnyyang (VulDB User), per the CVE Program record.