CVE-2024-48440
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 · uneditedShenzhen Tuoshi Network Communications Co.,Ltd 5G CPE Router NR500-EA RG500UEAABxCOMSLICv3.2.2543.12.18 was discovered to contain a command injection vulnerability via the component at_command.asp.
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 · moderate confidenceA command injection vulnerability exists in the at_command.asp web component of Shenzhen Tuoshi Network's 5G CPE Router NR500-EA (firmware v3.2.2543.12.18). The vulnerability allows remote attackers to execute arbitrary operating system commands via specially crafted input to this AT command interface, likely through improper sanitization of user-supplied parameters.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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's web management interface and navigate to System Settings > Firmware Version, or use the command: cat /proc/version (if SSH/telnet access is available) to retrieve the exact firmware version installed.Affected if The firmware version matches v3.2.2543.12.18 or falls within an unknown range around this version on a Shenzhen Tuoshi Network NR500-EA device.
-
Verify at_command.asp component existsCheck if the web endpoint /at_command.asp is present and accessible on the router by attempting to access it via HTTP/HTTPS (e.g., http://<router-ip>/at_command.asp).Affected if The at_command.asp file exists and responds to requests, indicating the vulnerable component is present.
-
Confirm remote management is enabledIn the router's web UI, navigate to Advanced Settings > Remote Management or Security Settings > Remote Access to determine if remote management (HTTP/HTTPS from WAN) is enabled.Affected if Remote management is enabled and the router's web interface is accessible from WAN/IPv6 networks, exposing the vulnerable component to external attackers.
-
Check network exposure of web servicesPerform a port scan of the router's public IP address on ports 80 and 443 to determine if the web management interface is exposed to the internet.Affected if Ports 80 or 443 are open and reachable from external networks, meaning the at_command.asp component is remotely accessible.
A defender is affected if they have a Shenzhen Tuoshi Network NR500-EA CPE router running firmware v3.2.2543.12.18 (or an unpatched version) with the at_command.asp component accessible either locally or remotely, particularly 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 dataApply vendor-supplied firmware patch if available; otherwise restrict network access to the router's web management interface to trusted IPs only, disable remote management where possible, and monitor for indicators of compromise.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-48440 — 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-48440 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