Tx3 FirmwareOperating system · Tenda

CVE-2022-43028

CRITICAL · 9.8 CVSS v3.1 Published 2022-10-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 TX3 US_TX3V1.0br_V16.03.13.11_multi_TDE01 was discovered to contain a stack overflow via the timeZone parameter at /goform/SetSysTimeCfg.

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

Tenda TX3 router firmware US_TX3V1.0br_V16.03.13.11 contains a stack overflow vulnerability in the SetSysTimeCfg form handler. The timeZone parameter passed to /goform/SetSysTimeCfg is not properly bounds-checked before being copied to a stack-allocated buffer, allowing an attacker to overflow the stack with arbitrary data.

MitigationApply vendor firmware patch when available; in the interim, restrict access to the router's web management interface to trusted networks only and disable remote administration if enabled.

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
Tx3 FirmwareOperating system
Affected:= 16.03.13.11

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
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 checks

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

  1. Identify Tenda TX3 router on the network
    Check router model through device discovery, web interface login page, or DHCP fingerprints. Look for 'Tenda TX3' or 'TX3' in device identification.
    Affected if The device is not a Tenda TX3 router, then this CVE does not apply.
  2. Check installed firmware version
    Log into the router web interface and navigate to System Settings > Firmware Upgrade, or check the admin page for version information. Alternatively, inspect the firmware file if downloaded locally.
    Affected if Firmware version is exactly 16.03.13.11, indicating the affected version.
  3. Verify web management interface is accessible
    Attempt to access the router's web interface on the default IP (usually 192.168.0.1 or 192.168.1.1) via HTTP. Confirm the /goform/SetSysTimeCfg endpoint responds to POST requests.
    Affected if The web interface and SetSysTimeCfg endpoint are reachable from the attacker's network position.
  4. Check if remote administration is enabled
    In the router web interface, navigate to Advanced > Remote Management, or System Settings > Remote Access. Verify whether remote management via WAN is enabled.
    Affected if Remote administration is enabled, allowing unauthenticated attackers on the internet to reach the vulnerable endpoint.
  5. Confirm timeZone parameter processing exists
    Send a benign POST request to /goform/SetSysTimeCfg with a normal timeZone value and verify the router accepts and processes it. This confirms the vulnerable code path is present.
    Affected if The endpoint processes the timeZone parameter without immediate error, indicating the vulnerable handler is active.

The environment is affected if it is a Tenda TX3 router running firmware version 16.03.13.11 with the web management interface (especially the SetSysTimeCfg endpoint) accessible from an attacker's location, regardless of whether remote administration appears enabled in settings.

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 patch when available; in the interim, restrict access to the router's web management interface to trusted networks only and disable remote administration if enabled.

Fix this in Tx3 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-43028 — 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-2022-43028 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