⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Critical · CVSS 9.8 ⚠ ACTIVELY EXPLOITED — CISA KEV

How to Fix CVE-2019-16057: OS Command Injection in D-Link DNS-320 Storage Device

By Sai Kiran Pandrala

⚡ At a glance
SeverityCVSS 9.8 (Critical)
Actively exploited?Yes, listed in CISA KEV (added 2022-04-15, federal due date 2022-05-06). Known ransomware use.
AffectedDNS-320 Storage Device
Fixed inSee vendor advisory for the patched build for your version
Type (CWE)CWE-78: Improper Neutralization of Special Elements used in an OS Command
Actively exploited. Listed in the CISA Known Exploited Vulnerabilities catalog since 2022-04-15; federal civilian agencies must remediate by 2022-05-06. Patch on an emergency cycle if the system is internet-exposed.

What is CVE-2019-16057?

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

A successful exploit lets a remote attacker run arbitrary code on the target system. The fix is to install the patched build of D-Link DNS-320 Storage Device listed in the table above, then confirm the running version after the upgrade.

Am I affected?

Check your installed version of D-Link DNS-320 Storage Device against the Affected row above. If the build sits inside any of those ranges, treat the host as vulnerable until patched.

Read the version the same way you would for any maintenance task: the management console About page, the CLI version command, or the package manager record for the installed binary. The vendor advisory linked in the references is the authoritative source for the affected-build matrix.

How to fix CVE-2019-16057

The remediation is the patched build of D-Link DNS-320 Storage Device. The blocks below give you runnable commands for the platforms that ship this product, plus a full PowerShell and Bash script you can drop into your patch automation.


Setup -> Firmware Update -> Browse -> select patched .bin -> Upload -> Reboot
# Required firmware: see D-Link security advisory or later

Mitigation while you stage the patch


# Vendor advisory: https://www.ftc.gov/system/files/documents/cases/dlink_proposed_order_and_judgment_7-2-19.pdf
# Block remote management at the LAN edge
iptables -A INPUT -p tcp -m multiport --dports 80,443,8080 -s <admin-allowlist> -j ACCEPT
iptables -A INPUT -p tcp -m multiport --dports 80,443,8080 -j DROP

Full PowerShell remediation script (detect, back up, patch, verify, log)


<#
.SYNOPSIS  Remediates CVE-2019-16057 on Windows hosts.
.DESCRIPTION
  Detects current version of DNS-320 Storage Device, takes a config backup, applies the patched build
  (the patched build), confirms the upgrade, and writes a transcript to %ProgramData%\Patching.
#>
$ErrorActionPreference = 'Stop'
$logDir = "$env:ProgramData\Patching"
New-Item -ItemType Directory -Force -Path $logDir | Out-Null
Start-Transcript -Path "$logDir\CVE-2019-16057-$(Get-Date -Format yyyyMMdd-HHmmss).log"

try {
    Write-Host '[1/5] Detecting current version'
    $svc = Get-Service | Where-Object { $_.DisplayName -match 'DNS-320' } | Select-Object -First 1
    if ($svc) { Write-Host "  Service: $($svc.Name) state=$($svc.Status)" }

    Write-Host '[2/5] Backup config directory if present'
    $cfg = "$env:ProgramFiles\DNS-320"
    if (Test-Path $cfg) {
        $bak = "$logDir\CVE-2019-16057-backup-$(Get-Date -Format yyyyMMdd-HHmmss).zip"
        Compress-Archive -Path $cfg -DestinationPath $bak -Force
        Write-Host "  Backup -> $bak"
    }

    Write-Host '[3/5] Apply patch'
    try {
        winget upgrade --id <vendor.DNS-320> --accept-source-agreements --accept-package-agreements --silent
    } catch {
        Write-Warning "winget upgrade failed: $_  -- falling back to MSU/MSI installer"
        Start-Process msiexec.exe -ArgumentList '/i "C:\Temp\patched.msi" /qn /norestart' -Wait
    }

    Write-Host '[4/5] Verify version'
    Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5
    # Adapt the next line to your product's version file:
    Get-ChildItem "$env:ProgramFiles\DNS-320" -Recurse -Filter *.exe -ErrorAction SilentlyContinue |
        Select-Object -First 1 | ForEach-Object { $_.VersionInfo.FileVersion }

    Write-Host '[5/5] Restart service if needed'
    if ($svc) { Restart-Service $svc.Name }
    Write-Host "CVE-2019-16057 remediation complete"
} catch {
    Write-Error "CVE-2019-16057 remediation FAILED: $_"
    exit 1
} finally {
    Stop-Transcript
}

Full Bash remediation script (detect, back up, patch, verify, log)


#!/usr/bin/env bash
# remediate-cve-2019-16057.sh — detect, back up, patch, verify.
set -euo pipefail
LOG="/var/log/patching"
mkdir -p "$LOG"
STAMP="$(date +%Y%m%d-%H%M%S)"
LOGFILE="$LOG/CVE-2019-16057-$STAMP.log"
exec > >(tee -a "$LOGFILE") 2>&1

echo "[1/5] Detect installed DNS-320 Storage Device"
if command -v dpkg >/dev/null 2>&1; then
    dpkg -l | grep -i "dns-320" || true
elif command -v rpm >/dev/null 2>&1; then
    rpm -qa | grep -i "dns-320" || true
fi

echo "[2/5] Backup config"
for d in /etc/dns-320 /opt/dns-320 /usr/local/dns-320; do
    if [[ -d "$d" ]]; then
        tar czf "$LOG/CVE-2019-16057-$(basename $d)-$STAMP.tgz" "$d"
        echo "  Backup -> $LOG/CVE-2019-16057-$(basename $d)-$STAMP.tgz"
    fi
done

echo "[3/5] Apply patch (target: the patched build)"
if command -v apt-get >/dev/null 2>&1; then
    sudo apt-get update
    sudo apt-get install --only-upgrade "dns-320" -y
elif command -v dnf >/dev/null 2>&1; then
    sudo dnf upgrade "dns-320" --security -y
elif command -v yum >/dev/null 2>&1; then
    sudo yum update "dns-320" --security -y
elif command -v zypper >/dev/null 2>&1; then
    sudo zypper patch --category security
fi

echo "[4/5] Verify"
if systemctl status "dns-320" >/dev/null 2>&1; then
    sudo systemctl restart "dns-320"
    systemctl is-active "dns-320"
fi
command -v "dns-320" >/dev/null 2>&1 && "dns-320" --version || true

echo "[5/5] CVE-2019-16057 remediation script complete. Log: $LOGFILE"

If you can't patch immediately

Disable the vulnerable service until patched (Linux)


# Vendor advisory: https://www.ftc.gov/system/files/documents/cases/dlink_proposed_order_and_judgment_7-2-19.pdf
sudo systemctl disable --now <vulnerable-service>
# Confirm no listener remains on the affected port
sudo ss -lntp | grep -E ':(443|22|8080|3306)' || echo 'No listener on common mgmt ports'

How to verify the fix worked

  1. Re-run the version command from the fix section. The output must match the patched build listed in the vendor advisory for your branch.
  2. Re-run an authenticated vulnerability scan (Nessus, Qualys, OpenVAS, Defender Vulnerability Management) targeting the patched host. CVE-2019-16057 must no longer be reported.
  3. Pull the latest service logs and search for the exploitation signatures in the vendor advisory. Treat any match before the patch timestamp as a possible compromise: isolate the host, rotate credentials the affected process could see, and run a full IR triage.
  4. Confirm any compensating control you put in place (firewall rules, sysctl, registry edits) is either intentionally left in place or rolled back, with the change documented in your CMDB.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

Is CVE-2019-16057 being exploited right now?

Yes. CVE-2019-16057 is in the CISA Known Exploited Vulnerabilities catalog, added 2022-04-15. CISA only lists CVEs with confirmed active exploitation.

What is the CVSS score for CVE-2019-16057?

CVSS 9.8 (Critical). Use it together with your exposure picture (internet-facing first, then DMZ, then internal) when you set the patch order.

Can I run the fix without downtime?

It depends on the platform. Network appliances often support hitless HA upgrades (upgrade the standby, fail over, upgrade the former primary). Application servers usually need a service restart. Clustered services (Elasticsearch, Tomcat behind a load balancer, MySQL replicas) tolerate a rolling upgrade. Schedule a maintenance window if HA is not in place.

What if my version is not in the affected list?

Re-check the build string in the vendor advisory linked below. CVE records reflect the affected-products list at publication. Variants discovered later are added to the same advisory or a follow-up CVE.

References

*This guide was assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*