dbcve.org
G416 FirmwareOperating system · Dlink

CVE-2023-50205

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 chmod 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-21298.

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 D-Link G416 router contains a command injection vulnerability in its HTTP service on TCP port 80. The issue stems from insufficient validation of user-supplied input before passing it to a system call. Because authentication is not required and the vulnerability executes in the root context, an attacker with network proximity to the device can execute arbitrary code with full system privileges.

MitigationApply the vendor-supplied firmware patch when available. If no patch exists, restrict network access to the device via firewall rules or VLAN segmentation, and consider replacing the affected hardware.

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/marking to identify the exact model number
    Affected if Device is not a D-Link G416 router
  2. Check installed firmware version
    Log into the router web interface and navigate to the Status or Firmware Upgrade page to view the current firmware version. Alternatively, check the download file name if you have access to the firmware file.
    Affected if Firmware version is earlier than 1.09b01 (versions below this are affected)
  3. Verify HTTP service is accessible
    Attempt to access the router's IP address on TCP port 80 via a web browser or use a tool like netcat or nmap to confirm port 80 is open and responding
    Affected if HTTP service on port 80 is accessible from the network segment being assessed
  4. Confirm no authentication is required for the vulnerable endpoint
    The vulnerability does not require authentication - if the HTTP interface is reachable and responds to requests without login, the command injection vector is present
    Affected if HTTP interface responds without requiring authentication

The device is affected if it is a D-Link G416 router running firmware versions prior to 1.09b01 with the HTTP service (port 80) accessible from the network being assessed.

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 the vendor-supplied firmware patch when available. If no patch exists, restrict network access to the device via firewall rules or VLAN segmentation, and consider replacing the affected hardware.

Recommended fix High confidence

1.09b01

  1. 1. Download the firmware version 1.09b01 or later from the official D-Link support website
  2. 2. Access the D-Link G416 router's web management interface
  3. 3. Navigate to the firmware upgrade section (usually under Administration > Firmware Upgrade)
  4. 4. Upload the downloaded firmware file
  5. 5. Wait for the upgrade process to complete and the router to reboot
  6. 6. Verify the firmware version has been updated to 1.09b01 or later

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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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