Command InjectionWeakness · CWE-77

CVE-2024-48441

HIGH · 8.8 CVSS v3.1 Published 2024-10-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
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
Wuhan Tianyu Information Industry Co., Ltd Tianyu CPE Router CommonCPExCPETS_v3.2.468.11.04_P4 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 confidence

The Tianyu CPE Router version CommonCPExCPETS_v3.2.468.11.04_P4 contains a command injection vulnerability in the at_command.asp web component. An attacker can inject and execute arbitrary operating system commands through unsanitized user input processed by this ASP page.

MitigationImplement strict input validation and sanitization on all user-supplied parameters in at_command.asp. Consider using parameterized commands or whitelist-based validation to prevent command injection. If possible, restrict access to this administrative interface.

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 checks

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

  1. Identify the CPE router model and firmware version
    Access the router's web management interface or check the device's system information page. Look for the firmware version string CommonCPExCPETS_v3.2.468.11.04_P4 or similar Tianyu CPE firmware versions.
    Affected if The firmware version matches CommonCPExCPETS_v3.2.468.11.04_P4 or falls within the Tianyu CPE firmware line containing this web component.
  2. Confirm the at_command.asp component exists
    Attempt to access the URL path /at_command.asp on the router's web interface (e.g., http://router-ip/at_command.asp). Check if the page loads or returns a valid HTTP response.
    Affected if The at_command.asp page is present and accessible, indicating the vulnerable component is enabled.
  3. Verify remote management access is enabled
    Check the router's web interface settings for Remote Management or Web GUI access from WAN. Look for options like 'Enable Remote Management' or 'Allow management from WAN' that are turned on.
    Affected if Remote management access is enabled, allowing unauthenticated or weakly authenticated access from external networks.
  4. Check network exposure of the management interface
    Review firewall rules or access control lists to determine if the router's web management port (typically 80 or 443) is exposed to untrusted networks or the internet. Use external port scanning tools to confirm.
    Affected if The router's management interface is reachable from untrusted networks or the public internet.
  5. Assess authentication requirements for at_command.asp
    Test whether the at_command.asp endpoint requires authentication. Attempt to access it without logging in or with standard user credentials to see if command injection parameters are accepted.
    Affected if The endpoint accepts commands without proper authentication or input sanitization validation.

A user is affected if they operate a Tianyu CPE router with the CommonCPExCPETS_v3.2.468.11.04_P4 firmware where the at_command.asp component is accessible and the management interface is exposed to untrusted networks.

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

Implement strict input validation and sanitization on all user-supplied parameters in at_command.asp. Consider using parameterized commands or whitelist-based validation to prevent command injection. If possible, restrict access to this administrative interface.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-48441 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-48441 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