dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 9 Oct 2023.
Dir 905l FirmwareOperating system · Dlink

CVE-2014-8361

CRITICAL · 9.8 CVSS v3.1 Published 2015-05-01
Fix available
A fix is available. Upgrade to 1.15b01 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS 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
The miniigd SOAP service in Realtek SDK allows remote attackers to execute arbitrary code via a crafted NewInternalClient request, as exploited in the wild through 2023.

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 · high confidence

The miniigd SOAP service in Realtek SDK contains a remote code execution vulnerability. Attackers can exploit this by sending a crafted NewInternalClient SOAP request, allowing arbitrary code execution on affected devices. This is a critical vulnerability in embedded device firmware that has been actively exploited in the wild.

MitigationApply vendor-supplied firmware updates that include the patched Realtek SDK. If no update is available, network segmentation and firewall rules should restrict access to the miniigd service to trusted internal hosts only.

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
Dir 905l FirmwareOperating system
Affected:<= 2.05b01
Dir 605l FirmwareOperating system
Affected:<= 1.14b06<= 2.07b02<= 3.03b07
Dir 600l FirmwareOperating system
Affected:<= 1.15<= 2.056b06
Dir 619l FirmwareOperating system
Affected:<= 1.15<= 2.07b02
Dir 809 FirmwareOperating system
Affected:<= 1.04b02
Dir 900l FirmwareOperating system
Affected:< 1.15b01
Realtek SdkApplication
Affected:all versions
Dir 501 FirmwareOperating system
Affected:<= 1.01b04

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

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 device and firmware version
    Access the device admin interface or check the firmware version via CLI (often via cat /proc/version, nvram get firmware_version, or similar). For D-Link devices, check the web UI status page or use 'nvram show' via telnet/SSH if available.
    Affected if The firmware version falls within or below these ranges: Dir 905l <= 2.05b01, Dir 605l <= 1.14b06/2.07b02/3.03b07, Dir 600l <= 1.15/2.056b06, Dir 619l <= 1.15/2.07b02, Dir 809 <= 1.04b02, Dir 900l < 1.15b01, Dir 501 <= 1.01b04, or the device uses Realtek SDK with unknown version.
  2. Confirm the miniigd or UPnP IGD service is running
    Check running processes via 'ps' command or examine /proc/<pid>/cmdline if you have shell access. Look for miniigd, igd, or upnpd processes. Alternatively, perform a port scan targeting UPnP ports (typically 49152-49155, 1900 for SSDP).
    Affected if The miniigd service, UPnP IGD daemon, or related processes are active on the device.
  3. Verify the NewInternalClient SOAP action is exposed
    Send a crafted SOAP request to the UPnP service endpoint on port 49152 (or whichever port the service listens on). The NewInternalClient action is typically at /ctl/IGD or /upnp/control/igd. Example using curl: curl -X POST -d '@soap_request.xml' http://<device_ip>:<port>/ctl/IGD where the SOAP body contains NewInternalClient with arbitrary execution instructions.
    Affected if The device accepts and processes the NewInternalClient SOAP action without authentication, returning a successful response.
  4. Check if UPnP is enabled in device settings
    Log into the device web administration interface and navigate to Advanced > UPnP, or check via CLI: 'nvram get upnp_enable' or similar command depending on the device firmware.
    Affected if UPnP/IGD is enabled and the device meets the affected product and version criteria.

A device is likely affected if it runs a D-Link firmware version within the specified ranges or uses Realtek SDK, has the miniigd or UPnP IGD service enabled, and accepts unauthenticated NewInternalClient SOAP requests.

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
Upgrade available Upgrade to 1.15b01 or later
Fixed in 1.15b01
Interim mitigation

Apply vendor-supplied firmware updates that include the patched Realtek SDK. If no update is available, network segmentation and firewall rules should restrict access to the miniigd service to trusted internal hosts only.

Recommended fix Moderate confidence

Latest available firmware from D-Link for the specific model (contact D-Link support if unsure)

  1. 1. Identify the exact D-Link router model from the affected list (Dir 905l, 605l, 600l, 619l, 809, 900l, or 501).
  2. 2. Visit the official D-Link support website (www.dlink.com) and navigate to the firmware download section for your specific model.
  3. 3. Check for available firmware updates. If the router model has reached end-of-life, no official firmware update may be available.
  4. 4. If firmware update is available, download the latest firmware version from D-Link's official site.
  5. 5. Access the router's web-based management interface (typically at 192.168.0.1 or 192.168.1.1).
  6. 6. Navigate to the firmware upgrade or system settings section.
  7. 7. Upload and apply the new firmware, following the on-screen instructions.
  8. 8. After the upgrade completes, verify the new firmware version in the router's status page.
Caveat Older D-Link router models may be end-of-life and no longer receive firmware updates; replacement with a supported router may be necessary

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

Fix this in Dir 905l Firmware Exploited in the wild — priority engagement
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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