dbcve.org
Dns 322l FirmwareOperating system · D Link

CVE-2014-7857

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
D-Link DNS-320L firmware before 1.04b12, DNS-327L before 1.03b04 Build0119, DNR-326 1.40b03, DNS-320B 1.02b01, DNS-345 1.03b06, DNS-325 1.05b03, and DNS-322L 2.00b07 allow remote attackers to bypass authentication and log in with administrator permissions by passing the cgi_set_wto command in the cmd parameter, and setting the spawned session's cookie to username=admin.

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-287

The mechanism that verifies who a user is can be side-stepped or fooled, letting an attacker act as someone they're not. Everything built on top of that identity then becomes untrustworthy. Fixing it means hardening the full authentication flow, including edge cases, tokens, and secondary paths.

General guidance for the improper authentication 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 325 FirmwareOperating system
Affected:<= 1.05b03
Dns 345 FirmwareOperating system
Affected:<= 1.03b06
Dns 320b FirmwareOperating system
Affected:<= 1.02b01
Dnr 326 FirmwareOperating system
Affected:<= 1.40b03
Dns 327l FirmwareOperating system
Affected:<= 1.02
Dns 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-320L: firmware >=1.04b12; DNS-327L: firmware >=1.03b04 Build0119; DNR-326: firmware >1.40b03; DNS-320B: firmware >1.02b01; DNS-345: firmware >1.03b06; DNS-325: firmware >1.05b03; DNS-322L: firmware >2.00b07

  1. Identify your specific D-Link device model (DNS-322L, DNS-325, DNS-345, DNS-320B, DNR-326, DNS-327L, or DNS-320L)
  2. Visit the official D-Link support website and navigate to the firmware download section for your specific model
  3. Download the latest firmware version for your device (must be newer than the vulnerable version listed)
  4. Access your device's web management interface
  5. Locate the firmware upgrade section in System Settings or Administration
  6. Upload and apply the new firmware file
  7. Allow the device to complete the upgrade process and reboot
  8. Verify the new firmware version is installed by checking the system information page
Caveat Firmware upgrades on NAS devices may reset some configuration settings; backup configuration before upgrading and restore after

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 $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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