CVE-2024-31812
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 · uneditedIn TOTOLINK EX200 V4.0.3c.7646_B20201211, an attacker can obtain sensitive information without authorization through the function getWiFiExtenderConfig.
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 confidenceTOTOLINK EX200 V4.0.3c.7646_B20201211 wireless extender contains an unauthenticated information disclosure vulnerability in the getWiFiExtenderConfig function. An attacker with network access can retrieve sensitive configuration data (likely including WiFi credentials, network settings, or administrative parameters) without any authentication, exposing the device and connected networks to further attack.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 the EX200 firmware versionAccess the device web interface (usually at 192.168.0.254 or 192.168.1.1) and navigate to System Settings > Firmware Upgrade or Status page to view the installed firmware version. Alternatively, check via command line if telnet/SSH is enabled.Affected if The displayed firmware version is exactly 4.0.3c.7646_b20201211
-
Confirm device model is Totolink EX200Verify the device model number in the web interface status page or on the physical device label matches EX200.Affected if The device model is Totolink EX200 with the affected firmware version 4.0.3c.7646_b20201211
-
Check for unauthenticated access to getWiFiExtenderConfigSend an HTTP GET or POST request to the device endpoint (typically /cgi-bin/ or /usr/bin/ with the getWiFiExtenderConfig function) without providing any authentication credentials. Check if the response contains sensitive configuration data such as WiFi SSIDs, passwords, or administrative settings.Affected if The device returns sensitive configuration data without requiring any login credentials
-
Assess network exposureDetermine if the device management interface is accessible from untrusted networks. Check router/firewall rules to see if ports used by the device (HTTP/HTTPS for web interface) are exposed to the internet or guest networks.Affected if The device is reachable from untrusted network segments without firewall filtering
If the device is a Totolink EX200 running firmware version 4.0.3c.7646_b20201211 and the getWiFiExtenderConfig endpoint responds to unauthenticated requests with sensitive data, the environment is affected by this CVE.
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 dataSince no vendor patch is available for this firmware version, implement compensating controls: isolate the device in a restricted network segment, block external access via firewall, and consider replacing the device with a supported model. Monitor for unauthorized access attempts.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31812 — 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-31812 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