Cloudanix VulnDB

CVE-2024-31817

High · 7.5

CVSS

7.5

EPSS

55.3%

Published

Apr 8, 2024

CISA due date

—

Cloudanix analysis

Next patch cycle SSVC: Attend

Some TOTOLINK extender devices can reveal sensitive configuration information to anyone who can reach their management interface, even without a password.

Exploitation
Remote Unauthenticated
Attacker needs
None
Complexity
Low
Impact
Data Exposure
Component
Firmware
Class
Information Disclosure
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

CVE-2024-31817 is an unauthenticated information disclosure vulnerability in TOTOLINK EX200 firmware version V4.0.3c.7646_B20201211. The vulnerable getSysStatusCfg function can be accessed by a remote network attacker without authentication and may return sensitive system or configuration information. The primary technical impact is loss of confidentiality; the CVSS vector indicates network exploitability, low attack complexity, no required privileges, no user interaction, and high confidentiality impact, with no direct integrity or availability impact.

Why it matters to the business

Successful exploitation can expose sensitive router or extender configuration details that may help attackers map the network, identify device settings, or prepare follow-on attacks against the device or connected environment. Because this is remotely exploitable without credentials and has a high EPSS score, internet-exposed or untrusted-network-exposed TOTOLINK EX200 devices should be treated as higher priority even though it is not currently listed in CISA KEV and is not known to be used in ransomware campaigns.

How an attack unfolds

An attacker first identifies a reachable TOTOLINK EX200 device running the affected firmware version. They then send a crafted HTTP request to the device interface that invokes the getSysStatusCfg function without authenticating. If the device is vulnerable, it returns sensitive status or configuration data. The attacker can use that data to fingerprint the device, understand network configuration, identify firmware/version details, or support subsequent attacks such as credential attacks, exploitation of additional router vulnerabilities, or unauthorized changes if other weaknesses are present.

How to fix it

Upgrade affected TOTOLINK EX200 devices running firmware V4.0.3c.7646_B20201211 to a vendor-provided fixed firmware version if available. If no fixed firmware is available, replace the device with a supported model or apply compensating controls: disable remote administration from the internet, restrict management access to trusted administrative networks only, block access to the web management interface from untrusted segments, place the device behind a firewall, and ensure strong unique administrative credentials are configured. Treat exposed legacy firmware as unsafe if it cannot be updated.

How to confirm the fix worked

Inventory TOTOLINK EX200 devices and confirm firmware versions through the administrative interface, device banner, asset management data, or authenticated configuration review. Verify that no device remains on V4.0.3c.7646_B20201211. From an untrusted network segment, confirm that the web management interface and getSysStatusCfg-related functionality are not reachable without authentication. Validate firewall or ACL rules by testing that only approved administrative sources can connect to the device management interface.

Typical attack path

  1. Scan the internet or local network for exposed TOTOLINK EX200 web management interfaces.
  2. Fingerprint the device model and firmware version where possible.
  3. Send an unauthenticated request to the endpoint or handler that invokes getSysStatusCfg.
  4. Collect sensitive system status or configuration information returned by the device.
  5. Use the disclosed information to support follow-on reconnaissance, targeting, credential attacks, or exploitation of other device weaknesses.

How to detect it

To determine whether exploitation may have occurred, review HTTP access logs from the device if available, upstream reverse proxy logs if used, firewall connection logs, IDS/IPS alerts, and packet capture or network telemetry for requests to the device web interface that reference getSysStatusCfg. Focus on unauthenticated requests, requests from unknown external IP addresses, scanning behavior across multiple devices, and repeated HTTP GET or POST attempts to management CGI endpoints. Because many consumer and small-office network devices have limited local logging, absence of device logs does not rule out exploitation; correlate with perimeter firewall/NAT logs and network flow data showing inbound connections to the management interface. Also review subsequent activity for signs of follow-on reconnaissance or unauthorized device administration, including unexpected login attempts, configuration exports, DNS or gateway changes, new port forwards, or unusual outbound connections from the device.

  • getSysStatusCfg
  • /cgi-bin/cstecgi.cgi
  • "topicurl":"getSysStatusCfg"
  • GET /cgi-bin/cstecgi.cgi
  • POST /cgi-bin/cstecgi.cgi

What your security team should do

  • Identify all TOTOLINK EX200 devices, especially those reachable from the internet, guest networks, or other untrusted segments.
  • Prioritize remediation for devices running V4.0.3c.7646_B20201211 due to unauthenticated remote exploitability and elevated EPSS likelihood.
  • Upgrade to fixed firmware where available, or replace unsupported devices if no security update exists.
  • Disable internet-facing remote management and restrict device administration to trusted internal management networks.
  • Review perimeter firewall, NAT, and port-forwarding rules for unintended exposure of TOTOLINK management services.
  • Search historical web access logs, firewall logs, IDS/IPS events, and network telemetry for unauthenticated requests referencing getSysStatusCfg.
  • Monitor affected device traffic for repeated probing, unusual HTTP requests, or connections from unknown external IP addresses.

The record

In TOTOLINK EX200 V4.0.3c.7646_B20201211, an attacker can obtain sensitive information without authorization through the function getSysStatusCfg.

Affected packages

Ecosystem Package Introduced Fixed

Related vulnerabilities