dbcve.org
Lr1200gb FirmwareOperating system · Totolink

CVE-2024-0576

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability was found in Totolink LR1200GB 9.1.0u.6619_B20230130. It has been declared as critical. This vulnerability affects the function setIpPortFilterRules of the file /cgi-bin/cstecgi.cgi. The manipulation of the argument sPort leads to stack-based buffer overflow. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-250792. 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 confidence

A stack-based buffer overflow vulnerability exists in Totolink LR1200GB router firmware (v9.1.0u.6619_B20230130) in the setIpPortFilterRules function within /cgi-bin/cstecgi.cgi. The sPort argument is not properly validated before use, allowing an attacker to overflow the stack buffer via crafted HTTP requests and potentially achieve remote code execution with the privileges of the web server.

MitigationSince the vendor has not responded to the disclosure, immediately restrict network access to the device's web interface (port 80/443) using firewall rules or place the device behind a NAT/segmented network. Monitor for exploitation attempts and check periodically for firmware updates from Totolink.

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
Lr1200gb FirmwareOperating system
Affected:= 9.1.0u.6619_b20230130

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Access the router web interface or check device label/metadata to confirm the model is Totolink LR1200GB
    Affected if Device is not a Totolink LR1200GB, then not affected
  2. Check firmware version
    Log into the router web interface and navigate to the firmware/version information page, or use the command 'cat /etc/os.release' or 'ubootenv_get' via UART if accessible, to retrieve the installed firmware version
    Affected if Firmware version is 9.1.0u.6619_B20230130 exactly, then affected
  3. Verify vulnerable CGI binary exists
    Attempt to access the file /cgi-bin/cstecgi.cgi on the router web server via HTTP request (e.g., curl http://<router-ip>/cgi-bin/cstecgi.cgi)
    Affected if The CGI binary responds or is present on the device, then the vulnerable code path exists
  4. Check if IP Port Filter feature is enabled
    Log into the router web interface and navigate to the IP Port Filter or firewall rules configuration section (usually under Security or Firewall settings)
    Affected if The setIpPortFilterRules function is accessible and the feature is enabled, the vulnerable code path can be triggered
  5. Assess network exposure of web interface
    Check if router HTTP/HTTPS ports (80/443) are exposed to untrusted networks by scanning from an external host or reviewing firewall rules: nmap -p 80,443 <router-public-ip>
    Affected if Ports 80/443 are directly accessible from untrusted networks (internet), then the device is vulnerable to remote exploitation

If the device is a Totolink LR1200GB running firmware version 9.1.0u.6619_B20230130 and the web interface is network-accessible, the device is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the vendor has not responded to the disclosure, immediately restrict network access to the device's web interface (port 80/443) using firewall rules or place the device behind a NAT/segmented network. Monitor for exploitation attempts and check periodically for firmware updates from Totolink.

Fix this in Lr1200gb Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0576 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-0576 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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