dbcve.org
Dir 868l FirmwareOperating system · Dlink

CVE-2023-39667

CRITICAL · 9.8 CVSS v3.1 Published 2023-08-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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 DIR-868L fw_revA_1-12_eu_multi_20170316 was discovered to contain a buffer overflow via the param_2 parameter in the FUN_0000acb4 function.

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 buffer overflow vulnerability exists in D-Link DIR-868L routers running firmware fw_revA_1-12_eu_multi_20170316. The overflow is triggered through the param_2 parameter in the FUN_0000acb4 function, potentially allowing remote code execution.

MitigationThis is an end-of-life device with no available patch; implement network segmentation to isolate the device and consider replacement with a supported router. If the device must remain in service, restrict external access 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
Dir 868l FirmwareOperating system
Affected:= 1.12_eu_multi_20170316

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 (typically 192.168.0.1 or 192.168.1.1) and navigate to Status or Device Information page to confirm the model is D-Link DIR-868L
    Affected if Device is a D-Link DIR-868L router
  2. Check the installed firmware version
    In the router web interface, go to Administration > Firmware Upgrade or Status page to view the current firmware version. Alternatively, access via telnet/SSH if enabled and check system information
    Affected if Firmware version is exactly 1.12_eu_multi_20170316
  3. Verify the web management interface is accessible
    Confirm the router HTTP/HTTPS management interface is reachable on the local network or externally if port forwarding is configured
    Affected if The management interface is accessible and the vulnerable firmware version is running

A user is affected if they have a D-Link DIR-868L router running the exact firmware version 1.12_eu_multi_20170316 with the web management interface 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

This is an end-of-life device with no available patch; implement network segmentation to isolate the device and consider replacement with a supported router. If the device must remain in service, restrict external access via firewall rules.

Recommended fix Moderate confidence

Latest available DIR-868L firmware from D-Link support (check for versions beyond 1.12)

  1. 1. Visit the official D-Link support page at support.dlink.com and navigate to the DIR-868L product support section.
  2. 2. Download the latest available firmware version for the DIR-868L router.
  3. 3. Access the router's web administration interface by entering the router's IP address (typically 192.168.0.1) in a web browser.
  4. 4. Log in with administrator credentials.
  5. 5. Navigate to the 'System' or 'Management' settings section.
  6. 6. Select 'Firmware Upgrade' or 'Router Update' option.
  7. 7. Click 'Browse' or 'Choose File' and select the downloaded firmware file.
  8. 8. Click 'Upload' or 'Upgrade' to begin the firmware update process.
Caveat firmware updates on older discontinued routers may have limited functionality changes; ensure backup of router configuration before upgrading

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

Fix this in Dir 868l Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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