dbcve.org
G416 FirmwareOperating system · Dlink

CVE-2023-50217

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 rm 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-21811.

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 (port 80) within the awsfile rm functionality allows remote attackers to execute arbitrary commands as root due to insufficient validation of user-supplied input before passing it to a system call. No authentication is required.

MitigationApply vendor firmware update when available; meanwhile disable remote HTTP management or isolate device on restricted network segment to limit exposure.

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's web interface or check the device label to confirm the model is D-Link G416
    Affected if Device is not a D-Link G416 model - not affected
  2. Check the firmware version
    Log into the router web interface and navigate to the Status or Management page to view the firmware version, or use the command 'cat /proc/version' or 'nvram get firmware_version' via telnet/SSH if available
    Affected if Firmware version is 1.09b01 or higher - not affected (patched); version is below 1.09b01 or cannot be determined - potentially affected
  3. Verify HTTP service is accessible
    Attempt to access http://<router-ip>/ on port 80 from a network-connected host
    Affected if HTTP service returns a 404 error, connection refused, or service is not running - likely not vulnerable through this vector
  4. Test for awsfile rm functionality exposure
    Send a crafted HTTP request to the awsfile rm endpoint (e.g., curl -X POST http://<router-ip>/awsfile -d 'rm=/etc/passwd' or similar) and observe if the application processes the parameter without sanitization
    Affected if The awsfile rm functionality is not found or returns an error indicating the feature does not exist - likely not exploitable

The environment is affected if it is a D-Link G416 router running firmware version below 1.09b01 with the HTTP service (port 80) and awsfile rm functionality exposed and accessible.

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 update when available; meanwhile disable remote HTTP management or isolate device on restricted network segment to limit exposure.

Recommended fix High confidence

D-Link G416 Firmware version 1.09b01 or later

  1. Download firmware version 1.09b01 or later from D-Link's official support website (support.dlink.com)
  2. Access the D-Link G416 router web management interface via http://192.168.0.1 or http://routerlogin.net
  3. Navigate to the Administration or System Settings section
  4. Locate the Firmware Upgrade option
  5. Upload the downloaded firmware file (.bin)
  6. Wait for the upload and installation to complete - do not power off the router
  7. After reboot, verify the firmware version in the router settings to confirm successful upgrade
Caveat Firmware upgrades may reset router settings to defaults; back up configuration before upgrading if possible

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

Fix this in G416 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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