dbcve.org
G416 FirmwareOperating system · Dlink

CVE-2023-50208

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 ovpncfg 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-21441.

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 the ovpncfg component of D-Link G416 routers. The HTTP service on TCP port 80 copies user-supplied data to a fixed-length stack buffer without validating its length, allowing remote attackers to execute arbitrary code as root without authentication.

MitigationApply vendor firmware patches when available; until then, restrict network access to the router's management interface (TCP port 80) to minimize 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 router model
    Check the device label or web interface for the exact model number (typically found on a sticker on the device or in the web UI header)
    Affected if The device is not a D-Link G416 router (this CVE does not apply to other models)
  2. Determine the installed firmware version
    Access the router web interface (HTTP on port 80) and navigate to the Status or System Information page to view the firmware version; alternatively, check the firmware file if you have local access
    Affected if The firmware version is lower than 1.09b01 (versions prior to this are vulnerable)
  3. Verify the HTTP management service is enabled
    Attempt to connect to the router on TCP port 80 (HTTP) from the network; check the router's firewall or access control settings in the web interface under Security or Administration
    Affected if The HTTP service on TCP port 80 is exposed and accessible (this is the attack vector)
  4. Confirm ovpncfg component presence
    If you have SSH or telnet access to the router, look for the ovpncfg binary or configuration utility in the filesystem (typically under /usr/bin or /etc); otherwise, this check relies on firmware version
    Affected if The ovpncfg component exists on the device (the vulnerability is in this specific component)
  5. Check network exposure of management interface
    Review firewall rules, port forwarding settings, or WAN access configuration to determine if TCP port 80 is reachable from outside the local network
    Affected if TCP port 80 is reachable from untrusted networks (increases exploitability)

A D-Link G416 router with firmware version below 1.09b01 that has its HTTP service (TCP port 80) accessible is affected by this vulnerability and allows remote unauthenticated code execution as root.

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 patches when available; until then, restrict network access to the router's management interface (TCP port 80) to minimize exposure.

Recommended fix Moderate confidence

D-Link G416 Firmware version 1.09b01 or later

  1. Locate the D-Link G416 router administration interface by accessing its IP address in a web browser
  2. Navigate to the Firmware Upgrade or Management section in the router settings
  3. Download the latest firmware version 1.09b01 or later from the official D-Link support website (support.dlink.com)
  4. Upload the firmware file through the router's web interface and wait for the upgrade process to complete
  5. After the router reboots, verify the firmware version has been updated to 1.09b01 or later
Caveat Standard firmware upgrade风险 - ensure stable power during flashing process

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

Fix this in G416 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing10.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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