dbcve.org
Dns 322l FirmwareOperating system · D Link

CVE-2014-7859

CRITICAL · 9.8 CVSS v3.0 Published 2017-08-25
Fix available
A fix is available. Upgrade to after 2.00b07 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
Stack-based buffer overflow in login_mgr.cgi in D-Link firmware DNR-320L and DNS-320LW before 1.04b08, DNR-322L before 2.10 build 03, DNR-326 before 2.10 build 03, and DNS-327L before 1.04b01 allows remote attackers to execute arbitrary code by crafting malformed "Host" and "Referer" header values.

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
How this class of weakness works · CWE-119

The program reads or writes outside the bounds of an allocated buffer, corrupting adjacent memory. With crafted input an attacker can overwrite control data and, with effort, redirect execution to their own code. Remediation ranges from bounds checking and safe library functions to compiler mitigations, usually alongside a careful audit of the surrounding code.

General guidance for the memory buffer bounds error class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Dns 322l FirmwareOperating system
Affected:<= 2.00b07
Dns 320lw FirmwareOperating system
Affected:<= 1.03b04
Dnr 326 FirmwareOperating system
Affected:<= 1.40b03
Dns 327l FirmwareOperating system
Affected:<= 1.02
Dnr 320l FirmwareOperating system
Affected:<= 1.03b04

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.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 a release after 2.00b07
Recommended fix High confidence

DNS-320LW/DNR-320L: firmware 1.04b08 | DNS-322L: firmware 2.10 build 03 | DNR-326: firmware 2.10 build 03 | DNS-327L: firmware 1.04b01

  1. Identify the exact model number of your D-Link device (DNS-320LW, DNS-322L, DNR-320L, DNR-326, or DNS-327L)
  2. Navigate to the official D-Link support page and locate the firmware download section for your specific model
  3. Download the appropriate fixed firmware version: DNS-320LW/DNR-320L: 1.04b08 or higher; DNS-322L: 2.10 build 03 or higher; DNR-326: 2.10 build 03 or higher; DNS-327L: 1.04b01 or higher
  4. Access the device's web management interface using administrator credentials
  5. Locate the firmware upgrade section (typically under Maintenance or System settings)
  6. Upload the downloaded firmware file and initiate the upgrade process
  7. Wait for the device to complete the firmware update and reboot automatically
  8. Verify the firmware version has been successfully updated by checking the system information page
Caveat Firmware upgrades may reset some configuration settings; back up your configuration before upgrading and reapply after the update

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $3,550. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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