CVE-2024-42977: Tenda FH1206 · Out-of-bounds Write
Source CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 15 Aug 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
Given the absence of an official patch, organizations should implement immediate compensating controls. First, restrict access to the router's management interface by limiting exposure to trusted internal networks only and blocking external access via firewall rules. Disable remote management features if enabled. Monitor network traffic for unusual POST requests targeting the qos parameter or abnormal router behavior such as unexpected reboots. Employ network segmentation to isolate vulnerable devices from critical infrastructure. Consider deploying intrusion detection/prevention systems (IDS/IPS) with custom signatures to detect exploitation attempts targeting this vulnerability. Where feasible, replace affected Tenda FH1206 routers with alternative devices from vendors with timely security update practices. Stay alert for firmware updates or advisories from Tenda and apply patches promptly once available. Additionally, maintain regular backups of router configurations to facilitate quick recovery after an incident.
Description
Tenda FH1206 v02.03.01.35 was discovered to contain a stack overflow via the qos parameter in the fromqossetting function. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted POST request.