CVE-2024-30607: Tenda FH1203 v2.0.1.6 has a stack overflow
Source CVE Database V5
Not known to be exploited · CVSS 8.0 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 28 Mar 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
To mitigate CVE-2024-30607, organizations should first check for firmware updates from Tenda addressing this vulnerability and apply them promptly once available. In the absence of an official patch, network administrators should restrict access to the router's management interfaces to trusted hosts only and disable any unnecessary services that could be exploited. Implement network segmentation to isolate vulnerable devices from critical infrastructure and untrusted networks. Monitoring network traffic for unusual activity around the router can help detect exploitation attempts. Additionally, consider replacing affected devices with models from vendors with a stronger security track record if timely patches are not forthcoming. Employing strong authentication mechanisms and regularly auditing device configurations will further reduce risk. Finally, educating users about the risks of local network attacks and maintaining an inventory of vulnerable devices will support proactive defense.
Description
Tenda FH1203 v2.0.1.6 has a stack overflow vulnerability in the deviceId parameter of the saveParentControlInfo function.