dbcve.org
G416 FirmwareOperating system · Dlink

CVE-2023-50216

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 awsfile tar 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-21810.

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

Command injection vulnerability in D-Link G416 router's HTTP service on port 80. The flaw exists in the awsfile tar file handling functionality where user-supplied input is not properly validated before being used in a system call, allowing unauthenticated attackers to execute arbitrary code with root privileges.

MitigationApply vendor firmware updates when available; until then, restrict network access to the router's HTTP management interface to prevent unauthenticated attackers from reaching the vulnerable service.

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. Confirm device model is D-Link G416
    Access the router web interface or check the device label/metadata to verify the model number is G416
    Affected if The device is not a D-Link G416 model
  2. Check the installed firmware version
    Log into the router web interface and navigate to the firmware/version information page, or use the command 'cat /proc/version' or 'nvram get firmware_version' via telnet/SSH if available
    Affected if The firmware version is lower than 1.09b01 or cannot be determined
  3. Verify HTTP service is listening on port 80
    Run 'netstat -tulpn | grep :80' or 'nmap -p 80 <router-ip>' from a connected client to check if the HTTP service is active
    Affected if The HTTP service is listening on port 80 and the firmware version is below 1.09b01
  4. Check network exposure of the management interface
    Determine if the router HTTP interface is accessible from untrusted networks by reviewing firewall rules or performing an external port scan
    Affected if The router HTTP management interface is exposed to untrusted networks and the firmware is vulnerable

A user is affected if they have a D-Link G416 router with firmware version below 1.09b01 and the HTTP service on port 80 is accessible, even from within their local network.

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 updates when available; until then, restrict network access to the router's HTTP management interface to prevent unauthenticated attackers from reaching the vulnerable service.

Recommended fix High confidence

G416 Firmware version 1.09b01

  1. Visit the official D-Link support website and locate the G416 product page
  2. Download the firmware version 1.09b01 or later from the official D-Link support page
  3. Access the router's web management interface via TCP port 80 (http)
  4. Navigate to the firmware upgrade section (typically under Administration or System settings)
  5. Upload the downloaded firmware file and initiate the upgrade
  6. Wait for the upgrade to complete and the router to reboot
  7. After reboot, verify the firmware version has been updated to 1.09b01 or higher
Caveat Firmware upgrades may reset router configuration to defaults; backup settings before upgrading if needed

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
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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