G1 FirmwareOperating system · Tendacn

CVE-2021-45993

HIGH · 7.5 CVSS v3.1 Published 2022-02-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Tenda routers G1 and G3 v15.11.0.17(9502)_CN were discovered to contain a stack overflow in the function formIPMacBindModify. This vulnerability allows attackers to cause a Denial of Service (DoS) via the IPMacBindRuleIP and IPMacBindRuleMac parameters.

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 · moderate confidence

A stack buffer overflow vulnerability exists in the formIPMacBindModify function of Tenda G1 and G3 routers running firmware v15.11.0.17(9502)_CN. The vulnerability is triggered via specially crafted IPMacBindRuleIP and IPMacBindRuleMac parameters, allowing remote attackers to cause a Denial of Service by overflowing the stack and crashing the device.

MitigationApply vendor firmware update if available; otherwise, restrict network access to the router's management interface via firewall rules or network segmentation to prevent unauthorized access to the vulnerable function.

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
G1 FirmwareOperating system
Affected:= 15.11.0.17\(9502\)_cn
G3 FirmwareOperating system
Affected:= 15.11.0.17\(9502\)_cn

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the router model
    Locate the model label on the device or check the router admin interface system status page for the hardware version
    Affected if The device is not a Tenda G1 or G3 router (this CVE only affects those models)
  2. Check the firmware version
    Access the router admin interface and navigate to System Settings or Firmware Upgrade to view the current firmware version
    Affected if The firmware version is exactly 15.11.0.17(9502)_CN (only this specific version is listed as affected)
  3. Verify the IP-MAC binding feature exists
    Log into the router web interface and look for settings related to IP-MAC binding, usually under Security or Access Control settings
    Affected if The formIPMacBindModify function must be present in the firmware for the vulnerability to be exploitable
  4. Check if remote web management is enabled
    In the router admin interface, examine the WAN access or remote management settings (often under System Settings or Advanced)
    Affected if Remote management (HTTP/HTTPS from WAN) is enabled, as the vulnerability can be triggered remotely via specially crafted parameters

You are affected if you have a Tenda G1 or G3 router running firmware version 15.11.0.17(9502)_CN with the IP-MAC binding feature present and potentially remote management exposed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware update if available; otherwise, restrict network access to the router's management interface via firewall rules or network segmentation to prevent unauthorized access to the vulnerable function.

Fix this in G1 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-45993 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-45993 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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