CVE-2022-40105
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 formWifiMacFilterGet 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 formWifiMacFilterGet function of Tenda i9 router firmware v1.0.0.8(3828). Attackers can send a crafted string to overflow a buffer, causing denial of service. The vulnerability stems from insufficient bounds checking when processing MAC filter configuration requests.
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.
-
Identify device model as Tenda i9Check router label or web interface System/Status page for model nameAffected if Device is not a Tenda i9 router (different models have different firmware and vulnerabilities)
-
Check firmware versionAccess router web interface, navigate to System Settings or Administration > Firmware/Version. Compare version number to 1.0.0.8(3828)Affected if Firmware version is exactly 1.0.0.8(3828)
-
Confirm MAC filter feature existsLogin to router web interface and look for Wireless Settings or Security settings containing MAC Filter or Access ControlAffected if The MAC filter configuration page exists and is accessible (indicating the vulnerable function is present)
-
Check if remote management is enabledNavigate to Administration or System Tools > Remote Management. Look for settings like 'Enable Remote Management', 'WAN Access', or 'Remote Upgrade' that allow access from WAN IP addressesAffected if Remote management/WAN access is enabled, exposing the vulnerability to external attackers
-
Verify the vulnerable function is presentIf you have access to firmware binary (via firmware download or backup), search for string 'formWifiMacFilterGet' using strings or hex editorAffected if The function formWifiMacFilterGet exists in the firmware binary
You are affected if you are running Tenda i9 router with firmware version 1.0.0.8(3828) and the MAC filter feature is accessible, especially if remote management is enabled.
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 patch if available; otherwise restrict administrative access to trusted IPs only via firewall rules or disable remote management.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40105 — 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-40105 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