CVE-2024-0577VulnerabilityPublished 16 Jan 2024Updated 2 Jun 2025

CVE-2024-0577: Totolink LR1200GB · Stack-based Buffer Overflow

Affects Totolink LR1200GBSource CVE Database V5

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

8.8High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.9% chance of exploitation in 30 days – higher than 62% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Given the absence of an official patch, European organizations should immediately identify and inventory all Totolink LR1200GB devices running the vulnerable firmware version. Network segmentation should be enforced to isolate these devices from sensitive internal systems. Access to the router's management interface should be restricted using firewall rules, allowing only trusted IP addresses and disabling remote management if not essential. Employ network intrusion detection/prevention systems (IDS/IPS) to monitor and block suspicious requests targeting /cgi-bin/cstecgi.cgi endpoints. Consider deploying web application firewalls (WAF) with custom rules to detect and block malformed 'lang' parameter inputs indicative of exploitation attempts. Where possible, replace vulnerable devices with alternative models from vendors with active security support. Regularly monitor threat intelligence feeds for updates on exploit developments and vendor patches. Finally, implement strict logging and alerting on router access and anomalous behavior to enable rapid incident response.

Description

A vulnerability was found in Totolink LR1200GB 9.1.0u.6619_B20230130. It has been rated as critical. This issue affects the function setLanguageCfg of the file /cgi-bin/cstecgi.cgi. The manipulation of the argument lang leads to stack-based buffer overflow. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-250793 was assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, exploitation of this vulnerability could lead to full compromise of affected routers, enabling attackers to intercept, manipulate, or disrupt network traffic. This could result in data breaches, unauthorized access to internal systems, and potential lateral movement within corporate networks. The loss of router integrity and availability could disrupt business operations, especially for organizations relying on these devices for internet connectivity or VPN termination. Additionally, compromised routers could be leveraged as footholds for launching further attacks or as part of botnets, amplifying the threat landscape. The lack of vendor response and patch availability increases the window of exposure, making timely mitigation critical. Organizations in Europe with Totolink LR1200GB devices in their infrastructure face heightened risk, particularly those in sectors with stringent data protection requirements such as finance, healthcare, and critical infrastructure.

Summary

CVE-2024-0577 is a critical stack-based buffer overflow vulnerability identified in the Totolink LR1200GB router, specifically affecting firmware version 9.1.0u.6619_B20230130. The flaw exists in the setLanguageCfg function within the /cgi-bin/cstecgi.cgi endpoint, where improper handling of the 'lang' argument allows an attacker to overflow the stack buffer. This vulnerability can be exploited remotely without user interaction, requiring only low privileges (PR:L) on the device. The overflow can lead to arbitrary code execution, compromising confidentiality, integrity, and availability of the device. The CVSS v3.1 base score is 8.8, reflecting high severity with network attack vector, low attack complexity, and no user interaction needed. The public disclosure of the exploit details increases the risk of exploitation by threat actors targeting vulnerable devices. Given the critical nature of the flaw and the common use of Totolink LR1200GB routers in small to medium enterprises and home networks, this vulnerability poses a significant threat to network security.

CWE-121Stack-based Buffer Overflow (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #14
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
Architecture and Design
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Implementation
Implement and perform bounds checking on input.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 3 Jul 2025, 16:12 UTC

WeaknessesCWE-121

Technical details

References

Community reviews

Related threats