CVE-2024-4491
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability classified as critical was found in Tenda i21 1.0.0.14(4656). This vulnerability affects the function formGetDiagnoseInfo. The manipulation of the argument cmdinput leads to stack-based buffer overflow. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-263080. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceStack-based buffer overflow in Tenda i21 router firmware 1.0.0.14(4656) in the formGetDiagnoseInfo function. The cmdinput parameter is not properly bounds-checked before being copied to a stack buffer, allowing remote attackers to overflow the stack and potentially execute arbitrary code or cause denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0.0.14\(4656\)CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device modelCheck the router label or access the admin interface to confirm the model is Tenda I21Affected if Device is not a Tenda I21 router - this vulnerability only affects that specific model
-
Check firmware versionAccess the router admin interface (typically at 192.168.0.1) and navigate to System Settings or Firmware Upgrade to view the installed firmware version, or use the command 'cat /proc/version' via telnet/SSH if availableAffected if Firmware version is exactly 1.0.0.14(4656) - only this specific version is listed as affected
-
Verify web management interface is accessibleAttempt to access the router web interface on port 80/tcp from a browserAffected if The web management interface is exposed and accessible - the vulnerable formGetDiagnoseInfo function is accessed through this interface
-
Confirm the vulnerable function existsAccess the router web interface and look for diagnostic or network diagnostic features that would invoke the formGetDiagnoseInfo function, or send an HTTP request to the endpoint that handles this function (such as /goform/formGetDiagnoseInfo)Affected if The diagnostic feature or the formGetDiagnoseInfo endpoint is present and responds - this confirms the vulnerable code path exists
-
Check network exposure of management interfaceDetermine if the router management interface is accessible from outside the local network by testing remote IP access on port 80/tcp or performing a port scanAffected if The management interface is exposed to untrusted networks (WAN) rather than only accessible from LAN - this increases exploitability
You are affected if you have a Tenda I21 router running firmware version 1.0.0.14(4656) with the web management interface accessible, as the formGetDiagnoseInfo function contains the stack-based buffer overflow in the cmdinput parameter.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor firmware update if available; otherwise restrict management interface access to trusted networks and implement network segmentation to reduce attack surface exposure.
- Consultation6.0 h
- Implementation32.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $17,280.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4491 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-4491 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data