dbcve.org
G416 FirmwareOperating system · Dlink

CVE-2023-50210

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 httpd API-AUTH Digest Processing Stack-based Buffer Overflow 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 the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-21662.

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

Stack-based buffer overflow in D-Link G416 router's HTTP service (port 80) during API-AUTH Digest Processing. The vulnerability stems from insufficient validation of user-supplied data length before copying to a fixed-size stack buffer, enabling remote attackers to execute arbitrary code with root privileges without authentication.

MitigationApply vendor firmware updates when available; as an interim control, disable remote HTTP management or restrict management interface to trusted networks via firewall rules.

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 device model
    Access the router administration interface or check the device label to confirm the exact model is D-Link G416
    Affected if Device is not a D-Link G416 model
  2. Check firmware version
    Navigate to router admin panel (typically System > Firmware or Status page) and locate the firmware version string; alternatively, use command-line tools like 'cat /proc/version' or 'nvram get firmware_version' if SSH/telnet access is available
    Affected if Firmware version is lower than 1.09b01 or cannot be determined
  3. Verify HTTP service is enabled
    Confirm that the HTTP service (web management interface on port 80) is currently active on the router; check via 'netstat -tulpn | grep :80' if shell access exists, or attempt to access http://router-ip from a connected client
    Affected if HTTP service is running and responds to requests on port 80
  4. Assess network exposure of management interface
    Determine if the HTTP management interface is accessible from untrusted networks (WAN/Internet) rather than only from LAN; test by attempting to access the router's public IP on port 80 from an external location, or review firewall rules that permit or block inbound HTTP traffic
    Affected if HTTP management interface is exposed to untrusted networks or the Internet

Environment is affected if the device is a D-Link G416 router running firmware version prior to 1.09b01 with the HTTP service enabled 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 updates when available; as an interim control, disable remote HTTP management or restrict management interface to trusted networks via firewall rules.

Recommended fix High confidence

G416 Firmware version 1.09b01

  1. 1. Download the firmware version 1.09b01 or later from the official D-Link support website (support.dlink.com)
  2. 2. Access the D-Link G416 router web management interface
  3. 3. Navigate to the firmware upgrade section (typically under Administration > Firmware Upgrade or Settings > Maintenance)
  4. 4. Upload the downloaded firmware file (.bin or .img)
  5. 5. Wait for the upgrade process to complete - do not power off the device
  6. 6. After reboot, verify the firmware version has been updated to 1.09b01 or later
  7. 7. Confirm the HTTP service is functioning normally on port 80

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

Fix this in G416 Firmware Scoped from the published advisory
  • Consultation5.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,040
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,864.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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