CVE Alert: CVE-2025-60342 – n/a – n/a
CVE-2025-60342
Tenda AC6 V2.0 15.03.06.50 was discovered to contain a stack overflow in the page parameter in the addressNat function. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted input.
AI Summary Analysis
Risk verdict
External DoS via a crafted request could disrupt services, but exploitation state and broader urgency remain uncertain without KEV/EPSS or SSVC data.
Why this matters
A DoS against a network-facing component can impact uptime and user experience, driving support costs and potential service-level penalties. If attackers can trigger it remotely or via common network inputs, opportunistic actors may stress-test devices in consumer or small business deployments.
Most likely attack path
Attacker would need to send a specially crafted input to the affected parameter-handling function; preconditions depend on whether the device exposes management interfaces to the network. Exploitation would mainly aim at stability disruption rather than data exfiltration, suggesting limited post-exploit reach unless additional access exists.
Who is most exposed
Devices with web-based or remote management exposed to LAN/WAN in consumer, small-business, or IoT gateway scenarios are at higher risk; home routers and similar embedded devices are typical targets in these patterns.
Detection ideas
- Unexplained service crashes or reboots associated with specific traffic patterns.
- Memory corruption symptoms in logs (crash titles, watchdog resets).
- Increased HTTP/management-port errors or timeouts during targeted input sequences.
- Crash dumps or stack traces in system logs following remote input attempts.
- PoC-like traffic bursts observed against the addressNat-like interface.
Mitigation and prioritisation
- Apply vendor-provided firmware updates when released; verify integrity before deployment.
- Enable network segmentation and restrict management interfaces to trusted networks.
- Disable or limit remote management exposure; require VPN or MFA for access.
- Monitor for PoC-like input patterns and implement rate limiting on critical parameters.
- If KEV is true or EPSS ≥ 0.5, treat as priority 1; otherwise prioritise based on asset exposure and uptime impact. Change-management: test in a staging environment prior to rollout; roll out in phased updates.
Support Our Work
A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.
If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.