CVE-2022-40101
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 · uneditedTenda i9 v1.0.0.8(3828) was discovered to contain a buffer overflow via the formWifiMacFilterSet function. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted string.
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 confidenceA buffer overflow vulnerability exists in the formWifiMacFilterSet function of Tenda i9 wireless router firmware v1.0.0.8(3828). The function fails to properly validate input length when processing WiFi MAC filter settings, allowing an attacker to send a crafted string that overflows a buffer and causes a Denial of Service condition.
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.8\(3828\)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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Tenda i9 router modelCheck the router label or web interface for the exact model number to verify it is a Tenda i9 deviceAffected if The device is not a Tenda i9 model, then it is not affected by this specific CVE
-
Check firmware versionAccess the router web interface (typically at 192.168.0.1) and navigate to System Settings or Administration > Firmware Upgrade to view the installed firmware version, or check the version file via telnet/SSH if availableAffected if The firmware version is exactly 1.0.0.8(3828), then it matches the affected version
-
Verify WiFi MAC filter feature existsLog into the router web interface and locate the WiFi MAC filter settings page, typically under Wireless Settings or Advanced Wireless settingsAffected if The MAC filter feature exists and is accessible, then the vulnerable code path is present in the firmware
-
Check for denial of service symptomsIf the MAC filter was recently configured, check if the router has become unresponsive, lost connectivity, or requires a reboot. Review system logs if available via the web interface or telnet/SSHAffected if The router exhibits unexpected crashes or unresponsiveness after MAC filter configuration, it may indicate exploitation of this buffer overflow
A Tenda i9 router running firmware version 1.0.0.8(3828) with an accessible WiFi MAC filter feature is affected by this vulnerability.
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 updates when available; if no update exists, consider disabling the WiFi MAC filter feature, implementing network segmentation to limit router exposure, or deploying compensating controls such as WAF/IPS to detect exploitation attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40101 — 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-2022-40101 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