dbcve.org
QurouterOperating system · Qnap

CVE-2024-48861

HIGH · 7.8 CVSS v3.1 Published 2024-11-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
An OS command injection vulnerability has been reported to affect several product versions. If exploited, the vulnerability could allow local network attackers to execute commands. We have already fixed the vulnerability in the following versions: QuRouter 2.4.4.106 and later

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

OS command injection vulnerability in QuRouter allows attackers on the local network to execute arbitrary OS commands, likely through unsanitized input being passed to system() or similar functions.

MitigationUpgrade QuRouter to version 2.4.4.106 or later. If immediate patching is not possible, restrict network access to the device and monitor for suspicious activity.

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
QurouterOperating system
Affected:= 2.4.0.190= 2.4.1.172= 2.4.1.634= 2.4.2.317= 2.4.2.538= 2.4.3.103

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 checks

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

  1. Identify QuRouter version via web interface
    Log into the QuRouter admin panel and navigate to System Settings > Firmware or System Status to view the current firmware version
    Affected if The displayed version matches any of these: 2.4.0.190, 2.4.1.172, 2.4.1.634, 2.4.2.317, 2.4.2.538, 2.4.3.103
  2. Identify QuRouter version via CLI
    Access the device via SSH or telnet and run the command: cat /proc/version or ls -la /etc/version or firmware version command if available
    Affected if The version output matches any of the affected versions listed above
  3. Verify management interface accessibility
    Check if the QuRouter web management interface (typically ports 80 or 443) is reachable from the local network segment where untrusted devices may exist
    Affected if The web interface is accessible to other devices on the local network without additional authentication barriers
  4. Confirm remote management feature status
    In the QuRouter web UI, check System Settings > Administration or Network Management for any 'Remote Management' or 'Allow external access' settings
    Affected if Remote management or external access to the admin interface is enabled, expanding the attack surface to more network locations

You are affected if the installed QuRouter firmware version is one of the six listed affected versions AND the device management interface is accessible to network attackers.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade QuRouter to version 2.4.4.106 or later. If immediate patching is not possible, restrict network access to the device and monitor for suspicious activity.

Recommended fix High confidence

QuRouter 2.4.4.106 or later

  1. Check the current QuRouter firmware version via the admin interface or command line
  2. Download QuRouter firmware version 2.4.4.106 or later from the official QNAP website (www.qnap.com)
  3. Apply the firmware update following QNAP's standard upgrade procedure
  4. After reboot, verify the new version is installed and the device is functioning normally

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Qurouter Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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