basicsecurity.net
Proof, not just disclosure.
Threats / D-Link / CVE-2019-16057
CVE-2019-16057 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

D-Link DNS-320 Storage Device vulnerability

The login_mgr.cgi script in D-Link DNS-320 storage devices contains a command injection vulnerability allowing unauthenticated remote code execution.

Verdict

Today item, not a backlog item.

This vulnerability enables attackers to execute arbitrary commands on affected DNS-320 devices without authentication. Active exploitation and ransomware campaigns have been documented, making this a critical threat to organizations using these network storage appliances.

CISA KEV Yes · 2022-04-153Ransomware use Flagged3EPSS 0.8721 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
10 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-04-15), flagged for known ransomware use.
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.8721 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: D-Link, DNS-320 Storage Device. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-78 OS Command Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious HTTP request to the login_mgr.cgi endpoint with injected shell commands.
Business
The organization's network-attached storage becomes compromised without any legitimate user interaction or credentials required.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I gain code execution privileges on the device and establish persistent access or deploy ransomware payloads.
Business
Critical data stored on the DNS-320 is encrypted, deleted, or exfiltrated, disrupting business operations and causing potential data loss.
3

Lateral reach — past segmentation narrative 3

Attacker
I use the compromised storage device as a pivot point to move laterally within the internal network.
Business
The breach expands beyond the storage device to other systems, increasing incident scope, recovery costs, and regulatory exposure.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • Ransomware-use flag (CISA)
  • EPSS probability (FIRST)
  • 10 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by mitre (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by mitreCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.