CVE-2022-43024
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 TX3 US_TX3V1.0br_V16.03.13.11_multi_TDE01 was discovered to contain a stack overflow via the list parameter at /goform/SetVirtualServerCfg.
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 confidenceA stack-based buffer overflow vulnerability exists in the Tenda TX3 router's web interface at the /goform/SetVirtualServerCfg endpoint. The 'list' parameter from HTTP POST requests is copied to a stack buffer without proper length validation, allowing an unauthenticated attacker to overflow the buffer and potentially execute arbitrary code with root 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= 16.03.13.11CVSS 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 modelAccess the router's web administration interface (typically at 192.168.0.1) and check the device model or system status page to confirm it is a Tenda TX3 router. Alternatively, check the device label or packaging.Affected if The device is not a Tenda TX3 router
-
Check the firmware versionIn the router's web admin interface, navigate to System Settings or Status page and locate the firmware version. It should display exactly 16.03.13.11. Alternatively, check the firmware file name if you have access to the firmware binary.Affected if The firmware version is not exactly 16.03.13.11
-
Verify the web interface is accessibleAttempt to access the router's web interface on port 80 or 443 (for example, by visiting http://192.168.0.1 in a browser). Confirm the page loads and presents a login or status page.Affected if The web interface is completely inaccessible from all network perspectives
-
Test for the vulnerable endpointSend a crafted HTTP POST request to the /goform/SetVirtualServerCfg endpoint with an abnormally long string in the 'list' parameter (for example, list=AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA where A is repeated hundreds of times). Observe if the router responds or if there is a noticeable delay, crash, or abnormal behavior.Affected if The endpoint exists and accepts the POST request without proper filtering
You are affected if your Tenda TX3 router runs firmware version 16.03.13.11 and the web interface (specifically the /goform/SetVirtualServerCfg endpoint) is accessible to the attacker.
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 dataRestrict WAN access to the router's web administration interface immediately. Contact Tenda for a firmware patch; if unavailable, consider replacing the device. If the device must remain in production, implement network-level filtering to block external access to port 80/443.
- Consultation4.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,496.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43024 — 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-43024 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