dbcve.org
G416 FirmwareOperating system · Dlink

CVE-2023-50215

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 nodered gz File Handling 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-21809.

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 routers contain a command injection vulnerability in the HTTP service on TCP port 80. The flaw exists due to insufficient validation of user-supplied input before passing it to a system call, allowing unauthenticated attackers to execute arbitrary code with root privileges.

MitigationApply vendor firmware patch when available; if no patch exists, consider network segmentation to limit exposure and monitor for compromise indicators on affected devices.

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
    Access the router admin interface or check the device label to confirm it is a D-Link G416 router
    Affected if The device is a D-Link G416 model
  2. Determine the firmware version
    Log into the router admin panel (typically at 192.168.0.1) and navigate to the Status or System Information page to view the firmware version, or use the command 'cat /proc/version' or 'sysinfo' via telnet/SSH if available
    Affected if The firmware version is lower than 1.09b01
  3. Verify HTTP service is exposed
    Confirm that the HTTP service on TCP port 80 is accessible from the network. This can be done by attempting to access http://[router-ip]/ from a browser or running 'nc -zv [router-ip] 80' from an external host
    Affected if Port 80 is open and the HTTP service responds to requests
  4. Confirm the vulnerability condition
    The vulnerability is exploitable via the HTTP interface without authentication. If the router is accessible on port 80 and the firmware version is below 1.09b01, the device is vulnerable to unauthenticated command injection
    Affected if Firmware version < 1.09b01 AND HTTP service on port 80 is accessible

The device is affected if it is a D-Link G416 router running firmware version lower than 1.09b01 with the HTTP service on port 80 exposed.

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 vendor firmware patch when available; if no patch exists, consider network segmentation to limit exposure and monitor for compromise indicators on affected devices.

Recommended fix Moderate confidence

Firmware version 1.09b01 or later

  1. Download the firmware version 1.09b01 or later from D-Link's official support website for the G416 router
  2. Access the router's web administration interface via HTTP on TCP port 80
  3. Navigate to the firmware upgrade section (typically under Administration or System Settings)
  4. Upload and apply the firmware version 1.09b01 or newer
  5. After the router reboots, verify the firmware version has been updated successfully
  6. Ensure the router's web interface is no longer exposed to the untrusted network if previously accessible

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

Fix this in G416 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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