CVE-2022-28496
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 · uneditedTOTOLink outdoor CPE CP900 V6.3c.566_B20171026 discovered to contain a command injection vulnerability in the setPasswordCfg function via the adminuser and adminpassparameter. 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 confidenceCommand injection vulnerability in TOTOLink CP900 V6.3c.566_B20171026 router firmware. The setPasswordCfg function fails to sanitize the adminuser and adminpass parameters, allowing attackers to inject and execute arbitrary OS commands by crafting malicious requests.
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= 6.3c.566_b20171026CVSS 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 router model and firmware versionLog into the TOTOLink router web interface (typically at 192.168.0.1) and navigate to System Status or Firmware Version page. Alternatively, check via command line if telnet/ssh is available.Affected if The device model shows CP900 and firmware version is exactly 6.3c.566_b20171026
-
Confirm setPasswordCfg function is presentIf you have access to the firmware binary, extract and examine the web server binary (typically httpd or webs) for the string 'setPasswordCfg' using binwalk or strings tools.Affected if The firmware binary contains the vulnerable setPasswordCfg function
-
Verify web management interface is accessibleAttempt to access the router's HTTP/HTTPS web interface from the network. Check if port 80 or 443 responds with the TOTOLink login page.Affected if The web management interface is exposed and responds to requests
-
Check if remote management is enabledIn the router web interface, navigate to Advanced Settings or Remote Management section. Look for options like 'Remote Management', 'Web Access from WAN', or 'Allow external access'.Affected if Remote management or WAN web access is enabled, making the vulnerable interface accessible from the internet
-
Inspect for signs of command injection compromiseReview router configuration backups or running config for unexpected entries. Check for new user accounts, unusual cron jobs, or modified network settings. Monitor router logs for suspicious POST requests to forms containing password or login endpoints.Affected if Unexpected administrative accounts exist, unusual processes or cron jobs are found, or logs show suspicious crafted requests to password configuration endpoints
A user is affected if they have a TOTOLink CP900 router running firmware version 6.3c.566_b20171026 with its web management interface accessible (especially from WAN), as this allows attackers to inject commands via the adminuser or adminpass parameters in the setPasswordCfg function.
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 dataUpdate router firmware to a patched version if available; otherwise, restrict administrative interface access to trusted networks only and disable remote management.
- Consultation4.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,912.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28496 — 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-28496 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