LiveActive security incident?Get immediate response
CVE Record

CVE-2019-16057: The login_mgr.cgi script in D-Link DNS-320 through 2.05.B10 is vulnerable to remote command injection.

The login_mgr.cgi script in D-Link DNS-320 through 2.05.B10 is vulnerable to remote command injection.

CriticalCVSS 9.8Known exploitedUpdated
Glexia's TakeHuman reviewedcritical

Security readout for executives and security teams

Plain-English summary

CVE-2019-16057 is a critical flaw in D-Link DNS-320 NAS login handling that can allow remote command execution. For executives, the business risk is full device compromise, data exposure, tampering, and service disruption if vulnerable devices remain reachable.

Executive priority

Treat this as urgent for any exposed or production DNS-320 device. Known exploitation plus unauthenticated remote command execution creates a realistic path to full device compromise and potential data loss.

Technical view

The CVE describes command injection in login_mgr.cgi on D-Link DNS-320 through 2.05.B10. CVSS 3.1 is 9.8: network-accessible, low complexity, no privileges, no user interaction, with high confidentiality, integrity, and availability impact. CWE-78 applies.

Likely exposure

Likely exposure is D-Link DNS-320 devices running firmware through 2.05.B10, especially if management or NAS services are reachable from untrusted networks. The bundle's structured affected product data is incomplete, so inventory confirmation is required.

Exploitation context

CISA KEV status indicates known exploitation. The provided bundle does not identify exploit timing, threat actors, prevalence, or campaign details. A public research reference exists, but this assessment does not rely on or repeat exploit mechanics.

Researcher notes

Evidence supports critical severity, CWE-78, unauthenticated network attack characteristics, and KEV exploitation status. The bundle does not provide a definitive vendor patch, CPE list, exploit prevalence, or forensic indicators, so validation should remain source-constrained.

Mitigation direction

  • Identify all D-Link DNS-320 assets and firmware versions.
  • Check D-Link or vendor guidance for available fixes or replacement advice.
  • Remove management interfaces from internet exposure immediately.
  • Restrict access to trusted administrative networks only.
  • Retire or replace unsupported vulnerable devices if no fix exists.
  • Monitor affected devices for suspicious process, login, and network activity.

Validation and detection

  • Confirm whether any DNS-320 device runs firmware through 2.05.B10.
  • Verify external attack surface scans do not expose the device interface.
  • Review firewall rules for inbound access to NAS administration services.
  • Check logs for unusual authentication, CGI, process, or outbound activity.
  • Document compensating controls if immediate replacement is not possible.
Prepared
Reviewed
Confidence
medium
Sources
5

Michael Williams reviewed this cited source version on .

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-78: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-16057 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2019-16057Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-78 · source CWE mapping

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.