G1 FirmwareOperating system · Tendacn

CVE-2021-45990

CRITICAL · 9.8 CVSS v3.1 Published 2022-02-04
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 routers G1 and G3 v15.11.0.17(9502)_CN were discovered to contain a command injection vulnerability in the function uploadPicture. This vulnerability allows attackers to execute arbitrary commands via the pic_name parameter.

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 confidence

Tenda G1 and G3 routers running firmware v15.11.0.17(9502)_CN contain a command injection vulnerability in the uploadPicture function. The pic_name parameter is not properly sanitized, allowing attackers to inject and execute arbitrary OS commands on the router through the web interface.

MitigationApply vendor firmware update when available; until then, disable remote web management via WAN, restrict admin interface access to trusted IPs only, and monitor for unauthorized access.

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
G1 FirmwareOperating system
Affected:= 15.11.0.17\(9502\)_cn
G3 FirmwareOperating system
Affected:= 15.11.0.17\(9502\)_cn

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 router model
    Log into the router web interface and check the device information page, or check the device label/marking to confirm it is a Tenda G1 or G3 router.
    Affected if The device is not a Tenda G1 or G3 router.
  2. Check firmware version
    In the router web interface, navigate to System Settings or Device Info to view the firmware version. Compare the displayed version to 15.11.0.17(9502)_CN.
    Affected if The firmware version is exactly 15.11.0.17(9502)_CN.
  3. Verify web management interface status
    Check if the router web interface is accessible from the network. For WAN exposure, check the router firewall or port forwarding settings to see if HTTP/HTTPS ports are forwarded or if remote management is enabled.
    Affected if The router web interface is accessible and the uploadPicture function exists.
  4. Confirm uploadPicture function presence
    The vulnerability exists in the uploadPicture function used for uploading images via the web interface. Check if the router firmware includes image upload or picture upload functionality in its web management features.
    Affected if The firmware includes the uploadPicture function and the pic_name parameter is processed without sanitization.

The environment is affected if the device is a Tenda G1 or G3 router running firmware version 15.11.0.17(9502)_CN and the web interface with upload functionality is accessible.

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 update when available; until then, disable remote web management via WAN, restrict admin interface access to trusted IPs only, and monitor for unauthorized access.

Fix this in G1 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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