dbcve.org
Cp900 FirmwareOperating system · Totolink

CVE-2022-28497

CRITICAL · 9.8 CVSS v3.1 Published 2023-03-23
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
TOTOLink outdoor CPE CP900 V6.3c.566_B20171026 is discovered to contain a command injection vulnerability in the mtd_write_bootloader function via the filename parameter. This vulnerability allows attackers to execute arbitrary commands via a crafted request.

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

OS command injection vulnerability in TOTOLink CP900 V6.3c.566_B20171026 firmware's mtd_write_bootloader function. The filename parameter is not properly sanitized, allowing attackers to inject arbitrary OS commands via crafted HTTP requests. Exploitable remotely without authentication.

MitigationApply vendor firmware patch if available; otherwise isolate or replace affected devices. Network segmentation and strict firewall rules can reduce attack surface until remediation is possible.

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
Cp900 FirmwareOperating system
Affected:= 6.3c.566_b20171026

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 TOTOLink CP900 device on the network
    Check device model label or scan network for TOTOLink CP900 MAC vendor OUI (Totolink products typically use specific MAC ranges). Access the device web interface and check the status or firmware page for model identification.
    Affected if The device is a TOTOLink CP900 unit
  2. Check firmware version
    Access the device web administration panel (typically at 192.168.0.1 or similar). Navigate to System Status, Firmware Version, or About page. Record the firmware version string displayed.
    Affected if Firmware version equals exactly 6.3c.566_b20171026
  3. Verify mtd_write_bootloader function is present
    Send a GET request to the device HTTP interface and examine the CGI or web server endpoints. The vulnerable function mtd_write_bootloader is typically accessed via the web interface. Check if /cgi-bin/mtd_write_bootloader or similar endpoint exists by reviewing the firmware binary or probing common paths.
    Affected if The mtd_write_bootloader function is exposed via the HTTP interface
  4. Assess network exposure of the web interface
    Determine if the device HTTP management port (80/443) is directly accessible from untrusted networks. Use port scanning (nmap -p 80,443 <device_ip>) to check if the web interface is reachable from outside the local network.
    Affected if The device HTTP interface is accessible from untrusted networks without firewall protection
  5. Check for signs of compromise
    Review device logs if accessible for unexpected HTTP requests, especially those containing shell metacharacters (;, |, &, `, $(), or backticks) in filename parameters. Look for unexpected new admin accounts, modified configurations, or unknown processes on the device.
    Affected if Log analysis reveals suspicious HTTP requests with command injection patterns or unexpected device behavior

You are affected if you have a TOTOLink CP900 device running firmware version 6.3c.566_b20171026 with the mtd_write_bootloader function exposed on an accessible HTTP interface.

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 if available; otherwise isolate or replace affected devices. Network segmentation and strict firewall rules can reduce attack surface until remediation is possible.

Fix this in Cp900 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-28497 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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