CVE-2024-0579
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 classified as critical was found in Totolink X2000R 1.0.0-B20221212.1452. Affected by this vulnerability is the function formMapDelDevice of the file /boafrm/formMapDelDevice. The manipulation of the argument macstr leads to command injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. 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 confidenceA command injection vulnerability exists in Totolink X2000R router firmware 1.0.0-B20221212.1452. The formMapDelDevice function in /boafrm/formMapDelDevice fails to properly sanitize the macstr parameter before passing it to a system call, allowing remote attackers to execute arbitrary commands on the underlying operating system.
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= 1.0.0-b20221212.1452CVSS 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.
-
Confirm Totolink X2000R modelAccess the router web interface or check the device label to verify the model number is X2000RAffected if The device is not a Totolink X2000R (different models may have different vulnerabilities)
-
Identify firmware versionLog into the router web interface and navigate to System Status or Firmware Upgrade page to view the installed firmware version. The version format is 1.0.0-B20221212.1452Affected if The firmware version is exactly 1.0.0-B20221212.1452 (this is the only affected version listed)
-
Check web management interface accessibilityAttempt to access the router's web interface over HTTP/HTTPS on the LAN or WAN IP address (typically ports 80 or 443)Affected if The web management interface is reachable from an untrusted network (the vulnerability is exploitable via this interface)
-
Verify vulnerable endpoint existsCheck if the /boafrm/formMapDelDevice endpoint is present by attempting a request to http://[router-ip]/boafrm/formMapDelDeviceAffected if The endpoint responds (indicates the vulnerable CGI module is loaded)
The device is affected only if it is a Totolink X2000R running firmware version 1.0.0-B20221212.1452 AND the web management interface is accessible to the attacker.
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 the vendor did not respond to the disclosure, no official patch exists. Organizations should immediately restrict access to the router's web management interface to trusted networks only, disable remote administration if enabled, and monitor for indicators of compromise. Consider replacing the device if remote management is required.
- Consultation4.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,064.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0579 — 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-0579 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