dbcve.org
G416 FirmwareOperating system · Dlink

CVE-2023-50200

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 cfgsave backusb 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-21288.

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 the HTTP service on D-Link G416 routers. The cfgsave backusb parameter lacks proper input validation, allowing attackers to inject arbitrary system commands. Exploitation requires no authentication and executes with root privileges.

MitigationApply vendor firmware update when released. Until then, disable remote HTTP management, restrict network access to the device, or isolate the device on a constrained network segment.

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 web interface or check the device label/marketing to confirm the model is D-Link G416
    Affected if The device is not a D-Link G416 router, then it is not affected by this specific CVE
  2. Check the 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 via CLI if accessible or examine the firmware file if extracted.
    Affected if The firmware version is 1.09b01 or higher, then the version is not in the affected range (< 1.09b01)
  3. Confirm HTTP management service is enabled
    Check the router web interface under Management or System settings for HTTP/HTTPS management access. Verify if the HTTP service is listening on the WAN interface or accessible remotely.
    Affected if The HTTP service is disabled or only accessible from LAN, the attack surface is reduced but the vulnerable code may still be present in the firmware
  4. Verify the cfgsave functionality exists
    Attempt to access the router's cfgsave endpoint via HTTP GET or POST request to /cfg or check the firmware binary for the cfgsave handler and backusb parameter handling.
    Affected if The cfgsave endpoint with backusb parameter is present and processes user input without sanitization, confirming the vulnerability exists in this firmware version

The device is affected if it is a D-Link G416 router running firmware version lower than 1.09b01, the HTTP service is enabled, and the vulnerable cfgsave backusb parameter is present in the firmware.

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 released. Until then, disable remote HTTP management, restrict network access to the device, or isolate the device on a constrained network segment.

Recommended fix High confidence

G416 Firmware version 1.09b01 or later

  1. 1. Download the firmware version 1.09b01 or later from the official D-Link support website for the G416 router
  2. 2. Access the router's web management interface by navigating to the device's IP address (typically 192.168.0.1)
  3. 3. Navigate to the Administration or System Settings section
  4. 4. Locate the Firmware Upgrade or Update section
  5. 5. Upload the downloaded firmware file and initiate the upgrade process
  6. 6. Wait for the upgrade to complete and the device to reboot
  7. 7. After reboot, verify the firmware version in the router's status page to confirm the update was successful
Caveat Firmware upgrades may temporarily disrupt network connectivity; ensure stable power during the update process

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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