dbcve.org
Command InjectionWeakness · CWE-77

CVE-2024-44335

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-7003G v19.12.24A1, 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 (RCE) via version_upgrade.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 DI-7003G and DI-7100/7200/7300/7400 series router models contain a Remote Command Execution vulnerability in the version_upgrade.asp functionality. Attackers can inject and execute arbitrary OS commands on the affected devices through this web interface component.

MitigationApply vendor firmware updates if available; if unsupported, restrict administrative access to trusted networks only or replace affected devices. Monitor for unauthorized access attempts.

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 your router model
    Check the product label on the device or log into the web administration interface and navigate to the status or device information page to confirm the exact model number (DI-7003G, DI-7003GV2, DI-7100G+V2, DI-7100GV2, DI-7200GV2, DI-7300G+V2, or DI-7400G+V2)
    Affected if The model matches one of the listed affected models
  2. Check your firmware version
    In the router web interface, locate the firmware version information (typically under Status, System Info, or Firmware Upgrade section) and compare it against any available vendor release notes
    Affected if You cannot verify that the firmware has been updated to a patched version
  3. Verify remote management access status
    In the router web interface, check the remote management or administration settings (usually under Advanced, Management, or Access Control) to determine if remote web interface access is enabled
    Affected if Remote management access to the web interface is enabled and the device is directly exposed to untrusted networks
  4. Confirm version_upgrade.asp is reachable
    From a system on the same network as the router, attempt to access http://[router-ip]/version_upgrade.asp using a web browser or curl command
    Affected if The page loads or returns any HTTP response, indicating the vulnerable endpoint is accessible

You are affected if your device is one of the listed D-Link DI-series models and remote management access to the web interface is enabled, allowing network attackers to reach the vulnerable version_upgrade.asp endpoint.

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 vendor firmware updates if available; if unsupported, restrict administrative access to trusted networks only or replace affected devices. Monitor for unauthorized access attempts.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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