dbcve.org
Command InjectionWeakness · CWE-77

CVE-2024-44334

HIGH · 8.8 CVSS v3.1 Published 2024-09-09
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
D-Link DI-7003GV2 v24.04.18D1, DI-7100G+V2 v24.04.18D1, DI-7100GV2 v24.04.18D1, DI-7200GV2 v24.04.18E1, DI-7300G+V2 v24.04.18D1, and DI-7400G+V2 v24.04.18D1 are vulnerable to Remote Command Execution due to insufficient parameter filtering in the CGI handling function of upgrade_filter.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

Multiple D-Link router models (DI-7003GV2, DI-7100G+V2, DI-7100GV2, DI-7200GV2, DI-7300G+V2, DI-7400G+V2) running firmware v24.04.18D1/18E1 contain an authenticated Remote Command Execution vulnerability. The upgrade_filter.asp CGI script fails to properly filter user-supplied parameters, allowing attackers to inject and execute arbitrary operating system commands.

MitigationApply available firmware patches from D-Link; if no patch exists, disable remote management interfaces or place devices behind a VPN/firewall to limit exposure to authenticated attackers.

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 exact D-Link router model
    Log into the router web interface (typically at 192.168.0.1) and navigate to Status or System Information page to confirm the exact model number (DI-7003GV2, DI-7100G+V2, DI-7100GV2, DI-7200GV2, DI-7300G+V2, or DI-7400G+V2). Alternatively, check the device label or use SSH/Telnet to run 'cat /proc/cpuinfo' or 'nvram get modelname'.
    Affected if The model is one of: DI-7003GV2, DI-7100G+V2, DI-7100GV2, DI-7200GV2, DI-7300G+V2, or DI-7400G+V2
  2. Check the installed firmware version
    In the router web interface, go to Status or Maintenance > Firmware Upgrade page to view the current firmware version. Alternatively, access via CLI and run 'nvram get firmware_version' or check the version displayed on the status page.
    Affected if The firmware version is 24.04.18D1 or 24.04.18E1
  3. Verify if remote management is enabled
    In the router web interface, go to Advanced > Remote Management or Access Control settings. Check if 'Enable Remote Management' or 'Allow WAN Access' is turned on for the web interface (port 80/443).
    Affected if Remote management/WAN access to the web interface is enabled, making the device reachable from the internet on HTTP/HTTPS ports
  4. Confirm the upgrade_filter.asp CGI script exists and is accessible
    Attempt to access the vulnerable script via browser or curl: http://<router-ip>/upgrade_filter.asp or https://<router-ip>/upgrade_filter.asp (if remote access is enabled). A 403 or 200 response indicates the script exists.
    Affected if The upgrade_filter.asp script is present and accessible (returns HTTP 200 or 403 instead of 404)
  5. Check for unexpected admin accounts or configuration changes
    In the router web interface, go to Administration > User Management or Account settings. Review the list of admin accounts for any unknown users. Also check System > Log for suspicious commands or login attempts from unfamiliar IP addresses.
    Affected if Unknown admin accounts exist, or logs show commands/activity from unauthorized sources

The device is affected if it is one of the listed D-Link models (DI-7003GV2, DI-7100G+V2, DI-7100GV2, DI-7200GV2, DI-7300G+V2, or DI-7400G+V2) running firmware version 24.04.18D1 or 18E1, and remote management is accessible from the network where attackers could reach the upgrade_filter.asp CGI script.

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

Apply available firmware patches from D-Link; if no patch exists, disable remote management interfaces or place devices behind a VPN/firewall to limit exposure to authenticated attackers.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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 locally
dbcve dependency scanner

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