CVE-2022-44174
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 AC18 V15.03.05.05 is vulnerable to Buffer Overflow via function formSetDeviceName.
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 formSetDeviceName function of Tenda AC18 router firmware version 15.03.05.05. The function fails to properly validate input length before copying data into a fixed-size buffer, allowing an attacker to overflow the buffer and potentially execute arbitrary code with elevated privileges on the device.
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= 15.03.05.05CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 the router modelCheck the device label or access the web管理界面 (usually at 192.168.0.1) and look for the model number in the system status or device info pageAffected if The device is not a Tenda AC18 router
-
Check the firmware versionAccess the router web interface, navigate to System Settings or System Status, and locate the firmware version field. Alternatively, check the firmware file name if you have access to the firmware dumpAffected if The firmware version is exactly 15.03.05.05 (only this specific version is listed as affected)
-
Verify the web management interface is accessibleAttempt to access the router login page via HTTP (typically http://192.168.0.1) from the local network or remotely if remote management is enabledAffected if The web interface responds and the formSetDeviceName function is present and accessible
-
Check if remote administration is enabledIn the router web interface, go to Advanced Settings or System Settings and look for Remote Management, Remote Access, or WAN Access options. Check if they are enabledAffected if Remote management is enabled, allowing potential attackers on the WAN to reach the vulnerable formSetDeviceName function
The device is affected only if it is a Tenda AC18 router running firmware version 15.03.05.05 with the web management interface (and specifically the formSetDeviceName function) accessible, especially if remote administration 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 any available firmware update from Tenda for the AC18 model. If no vendor patch exists, restrict network access to the router's management interface, disable remote administration, and consider network segmentation.
- Consultation4.0 h
- Implementation8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-44174 — 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-44174 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