dbcve.org
G416 FirmwareOperating system · Dlink

CVE-2023-50211

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 Timestamp 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-21663.

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

A stack-based buffer overflow vulnerability exists in the httpd service of D-Link G416 routers. The issue stems from insufficient validation of user-supplied data length in the API-AUTH timestamp processing function, allowing an attacker to overwrite stack memory and execute arbitrary code with root privileges by sending crafted HTTP requests to TCP port 80.

MitigationApply the vendor-supplied firmware update when available; if no patch exists, restrict network access to the router's management interface via firewall rules or disable remote administration.

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
    Log into the router's web interface or check the device label to confirm the model is D-Link G416
    Affected if The device is not a D-Link G416 router, then this CVE does not apply
  2. Check the installed firmware version
    Access the router's web interface (typically at 192.168.0.1) and navigate to the Status or Management section to view the firmware version, or use the command line and run 'cat /proc/version' or check '/etc/fw_info' if available
    Affected if The firmware version is lower than 1.09b01 (for example, 1.08 or earlier)
  3. Confirm the httpd service is running
    Access the router via SSH or telnet if enabled, then run 'ps | grep httpd' or 'ps aux' to list running processes
    Affected if The httpd process is running (this is typically the default state for these routers)
  4. Verify if the management interface is accessible on port 80
    Attempt to access http://[router-ip]/ from a client on the network, or run 'netstat -tulpn | grep :80' if you have CLI access
    Affected if TCP port 80 is open and responding to HTTP requests

A D-Link G416 router is affected if it is running firmware version lower than 1.09b01, has the httpd service running, and has port 80 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 the vendor-supplied firmware update when available; if no patch exists, restrict network access to the router's management interface via firewall rules or disable remote administration.

Recommended fix High confidence

D-Link G416 Firmware version 1.09b01

  1. Download the D-Link G416 firmware version 1.09b01 (or latest available) from the official D-Link support website (support.dlink.com)
  2. Access the D-Link G416 router's web management interface by navigating to the router's IP address (commonly 192.168.0.1) in a web browser
  3. Log into the router administrator interface with valid credentials
  4. Navigate to the 'Management' or 'System' settings section of the web interface
  5. Locate the 'Firmware Upgrade' or 'Router Upgrade' option
  6. Upload the downloaded firmware file (1.09b01) to the router
  7. Wait for the firmware upload and installation to complete - do not power off the router during this process
  8. After the router reboots, verify the firmware version has been updated to 1.09b01 in the system information section

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
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
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,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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