CVE-2024-45880
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 command injection vulnerability exists in Motorola CX2L router v1.0.2 and below. The vulnerability is present in the SetStationSettings function. The system directly invokes the system function to execute commands for setting parameters such as MAC address without proper input filtering. This allows malicious users to inject and execute arbitrary commands.
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 the SetStationSettings function of Motorola CX2L router firmware v1.0.2 and below. The function directly passes user-supplied parameters such as MAC addresses to the system() function without input sanitization, allowing authenticated attackers to inject and execute arbitrary operating system commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/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 firmware versionAccess the router admin web interface and navigate to Status or System settings to view the firmware version. Alternatively, check via CLI using 'cat /proc/firmware_version' or 'nvram get firmware_version' if SSH/telnet is available.Affected if The displayed firmware version is v1.0.2 or any version lower than v1.0.2.
-
Confirm router modelVerify the device is specifically a Motorola CX2L router by checking the product label, admin interface header, or via CLI command 'cat /proc/cpuinfo' or 'nvram get model_name'.Affected if The device model is confirmed as Motorola CX2L and the firmware version is v1.0.2 or below.
-
Check if admin interface is accessibleDetermine if the router web admin interface is exposed to the network. Attempt to access the router IP on the standard HTTP/HTTPS ports (80/443). Check firewall rules or port forwarding configurations that may expose the management interface.Affected if The admin interface is accessible from an attacker-controlled network, allowing authenticated command injection.
-
Verify SetStationSettings function existsIf you have access to the firmware binary or shell, search for the SetStationSettings function using 'grep -r SetStationSettings /' or examine the web server binary. Check if this function processes MAC address parameters.Affected if The SetStationSettings function is present and processes user-supplied MAC address parameters without visible sanitization routines.
If the Motorola CX2L router is running firmware v1.0.2 or below and has its admin interface accessible to an attacker, the command injection vulnerability in SetStationSettings can be exploited.
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 dataImplement strict input validation and sanitization for all parameters in SetStationSettings before executing system calls, or replace system() calls with safer APIs that do not involve shell interpretation.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45880 — 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-45880 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