CVE-2024-31806
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 EX200 V4.0.3c.7646_B20201211 was discovered to contain a Denial-of-Service (DoS) vulnerability in the RebootSystem function which can reboot the system without authorization.
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 confidenceThe TOTOLINK EX200 V4.0.3c.7646_B20201211 router contains an unauthenticated denial-of-service vulnerability in its RebootSystem function. An attacker can trigger a system reboot without any authorization by calling this function, causing service disruption.
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= 4.0.3c.7646_b20201211CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Check the device firmware versionAccess the router's web management interface and navigate to System Status or Firmware Upgrade page to view the current firmware version. Alternatively, check via CLI if SSH/Telnet is available using 'cat /proc/version' or '固件版本' command.Affected if The firmware version is 4.0.3c.7646_b20201211 exactly
-
Confirm management interface accessibilityDetermine if the router's HTTP/HTTPS management interface (typically on ports 80/443 or 8080) is reachable from untrusted networks. Use 'netstat -an' or nmap scanning from an external host to identify exposed management ports.Affected if The management interface is exposed to the internet or untrusted LAN segments without firewall protection
-
Verify authentication is required for reboot functionAttempt to access the RebootSystem function endpoint without providing credentials. This may be at a URL like /cgi-bin/cstecgi.cgi with reboot-related parameters, or examine the device's CGI/JSON API endpoints to identify unauthenticated reboot triggers.Affected if The reboot function can be triggered via HTTP/HTTPS request without any authentication token or session cookie
-
Check for unauthorized access to cstecgi.cgi endpointInspect the router's web server configuration and examine the cstecgi.cgi binary or its handling code to verify if the reboot operation validates user sessions before executing.Affected if The reboot operation lacks session validation or accepts requests without valid authentication credentials
The device is affected if it runs firmware version 4.0.3c.7646_b20201211 and its management interface or reboot API endpoint is accessible without authentication.
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 dataImplement proper authentication and authorization checks on the RebootSystem function to ensure only authenticated administrators can trigger reboots. Until a patched firmware is available, restrict network access to the device's management interface.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31806 — 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-2024-31806 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