dbcve.org
G416 FirmwareOperating system · Dlink

CVE-2023-50206

HIGH · 8.8 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.09b01 or later.
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 G416 flupl query_type edit Command Injection Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of D-Link G416 routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the HTTP service listening on TCP port 80. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-21299.

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

D-Link G416 router contains a command injection vulnerability in the HTTP service on TCP port 80. The query_type parameter lacks proper input validation, allowing attackers to inject arbitrary system commands that execute with root privileges. No authentication is required.

MitigationApply available firmware updates from D-Link. If no update exists, restrict access to the router's management interface or consider device replacement.

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
G416 FirmwareOperating system
Affected:< 1.09b01

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 device model
    Check the router label or access the web interface and look for the model number in the device info or status page
    Affected if The device is not a D-Link G416 model
  2. Check the firmware version
    Access the router's web interface (typically at 192.168.0.1 or 192.168.1.1), navigate to the status or system info page, and record the firmware version listed
    Affected if The installed firmware version is anything earlier than 1.09b01 (e.g., 1.08, 1.07, etc.)
  3. Confirm HTTP service is enabled
    Attempt to access the router's web interface on TCP port 80 (e.g., visit http://[router-ip] in a browser)
    Affected if The HTTP management interface is accessible and responds
  4. Verify the query_type parameter exists
    Submit a GET request to the router's HTTP interface and inspect the parameters accepted by the web application
    Affected if The query_type parameter is accepted by the web application without authentication

If the device is a D-Link G416 running firmware below version 1.09b01 and the HTTP management interface on port 80 is accessible, the device is affected by this vulnerability.

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.09b01 or later
Fixed in 1.09b01
Interim mitigation

Apply available firmware updates from D-Link. If no update exists, restrict access to the router's management interface or consider device replacement.

Recommended fix Moderate confidence

Firmware version 1.09b01 or later

  1. 1. Download the latest firmware version 1.09b01 or later from the official D-Link support website (support.dlink.com)
  2. 2. Access the D-Link G416 router web management interface via HTTP on TCP port 80
  3. 3. Navigate to the Administration or System Settings section
  4. 4. Locate the Firmware Upgrade option
  5. 5. Upload the downloaded firmware file and initiate the upgrade
  6. 6. Wait for the upgrade to complete and the device to reboot
  7. 7. Verify the firmware version has been updated to 1.09b01 or later in the web interface

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

Fix this in G416 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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