CVE-2024-0572
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 · uneditedA vulnerability, which was classified as critical, was found in Totolink LR1200GB 9.1.0u.6619_B20230130. Affected is the function setOpModeCfg of the file /cgi-bin/cstecgi.cgi. The manipulation of the argument pppoeUser leads to stack-based buffer overflow. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-250788. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceStack-based buffer overflow in the web CGI interface (cstecgi.cgi) of Totolink LR1200GB router firmware. The setOpModeCfg function fails to validate the length of the pppoeUser argument before copying it to a stack buffer, allowing remote attackers to overwrite return addresses and execute arbitrary code with root privileges.
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= 9.1.0u.6619_b20230130CVSS 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 device model and firmware versionAccess the router web interface (usually at 192.168.1.1) and check the status/page for model name (LR1200GB) and firmware version, or run 'cat /etc/os-release' or 'ubus call system board' via SSH/telnet if availableAffected if The device is Totolink LR1200GB with firmware version 9.1.0u.6619_b20230130 exactly
-
Verify cstecgi.cgi exists on the deviceAttempt to access http://[router-ip]/cstecgi.cgi or check if the file exists via SSH/telnet at /www/cgi-bin/cstecgi.cgiAffected if The CGI binary cstecgi.cgi is present and accessible on the device
-
Check if remote management is enabledLog into the router web interface, navigate to Advanced/Management settings, and check if 'Remote Management' or 'Web Access from WAN' is enabledAffected if Remote management or WAN web access is enabled, making the vulnerable CGI interface reachable from the internet
-
Verify network exposure of web interfaceScan the router's WAN IP port 80/443 or check router firewall rules to see if the web interface is exposed to untrusted networksAffected if The router web management interface (port 80/443) is directly accessible from the WAN/internet
The device is affected if it is a Totolink LR1200GB running firmware version 9.1.0u.6619_b20230130 and the cstecgi.cgi web interface is accessible, especially if remote management is enabled.
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 dataImmediately restrict access to the router's web management interface to trusted IPs only, disable remote management if enabled, and replace the device with a supported alternative as no vendor patch is available.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0572 — 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-0572 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