Dir 300 FirmwareOperating system · Dlink

CVE-2013-7471

CRITICAL · 9.8 CVSS v3.1 Published 2019-06-11
Fix available
A fix is available. Upgrade to 1.02b03 / 1.04b11 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable 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
An issue was discovered in soap.cgi?service=WANIPConn1 on D-Link DIR-845 before v1.02b03, DIR-600 before v2.17b01, DIR-645 before v1.04b11, DIR-300 rev. B, and DIR-865 devices. There is Command Injection via shell metacharacters in the NewInternalClient, NewExternalPort, or NewInternalPort element of a SOAP POST request.

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
How this class of weakness works · CWE-77

User input reaches a command interpreter without being fully separated from the command itself, so an attacker can append instructions of their own. Because those run with the application's privileges, it frequently means control of the host. The lasting fix is to avoid constructing commands from input — call APIs directly and pass arguments as data, never as concatenated strings.

General guidance for the command injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Dir 300 FirmwareOperating system
Affected:= 2.14b01
Dir 600 FirmwareOperating system
Affected:< 2.17b01
Dir 645 FirmwareOperating system
Affected:< 1.04b11
Dir 845 FirmwareOperating system
Affected:< 1.02b03
Dir 865 FirmwareOperating system
Affected:= 1.05b03

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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
Upgrade available Upgrade to 1.02b03 / 1.04b11 / 2.17b01 or later
Fixed in 1.02b031.04b112.17b01
Recommended fix High confidence

Model-specific firmware: DIR-600 to v2.17b01+, DIR-645 to v1.04b11+, DIR-845 to v1.02b03+ (or later versions from D-Link support)

  1. 1. Identify the exact model of the D-Link DIR router from the affected list (DIR-300 rev B, DIR-600, DIR-645, DIR-845, or DIR-865).
  2. 2. Access the router's web administration interface by entering the router's IP address in a web browser.
  3. 3. Log in with administrator credentials.
  4. 4. Navigate to the 'Firmware' or 'System' section of the router settings.
  5. 5. Locate the firmware update option and download the appropriate fixed firmware version for the specific model: For DIR-600, upgrade to version 2.17b01 or later; For DIR-645, upgrade to version 1.04b11 or later; For DIR-845, upgrade to version 1.02b03 or later; For DIR-300 rev B and DIR-865, check D-Link's support website for the latest available firmware.
  6. 6. Upload the firmware file and allow the router to complete the update process, which may take several minutes.
  7. 7. After the router reboots, verify the firmware version has been updated successfully.
  8. 8. Change the router admin password as a security best practice after the update.
Caveat Firmware updates may reset router configurations to defaults; back up configuration before upgrading and reapply settings after the update.

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,550. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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