basicsecurity.net
Proof, not just disclosure.
Threats / QNAP / CVE-2018-19949
CVE-2018-19949 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

QNAP Network Attached Storage (NAS) vulnerability

Command injection in QNAP NAS File Station allows remote attackers to execute arbitrary commands on affected devices.

Verdict

Today item, not a backlog item.

A command injection vulnerability in QNAP Network Attached Storage systems enables unauthenticated remote code execution. The flaw has been exploited in the wild and leveraged in ransomware campaigns, posing significant risk to enterprise and consumer NAS deployments.

CISA KEV Yes · 2022-05-243Ransomware use Flagged3EPSS 0.24449 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
4 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-05-24), flagged for known ransomware use.
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.24449 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: QNAP, Network Attached Storage (NAS). Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-20 Improper Input Validation, CWE-77 Command Injection, 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 request to the File Station interface containing shell metacharacters to break out of intended command boundaries.
Business
Attackers gain initial remote code execution on the NAS without authentication, establishing a foothold in the network.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I execute system commands with the privileges of the NAS service process to enumerate the device and connected network.
Business
The NAS becomes a pivot point for lateral movement into the broader network infrastructure and data repositories.
3

Lateral reach — past segmentation narrative 3

Attacker
I deploy ransomware payloads or data exfiltration tools directly onto the compromised NAS.
Business
Critical backup and file storage systems are encrypted or stolen, disrupting business continuity and triggering data breach notifications.
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)
  • 4 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by qnap (CNA)
  • Named finder/reporter credit (CVE.org)
  • 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.
  • Disclosure & credit2
    Catalogued by qnapCNA