Media Streaming Add OnPlugin / extension · Qnap

CVE-2017-7640

CRITICAL · 9.8 CVSS v3.0 Published 2018-03-08
Fix available
A fix is available. Upgrade to after 430.1.2.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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
QNAP NAS application Media Streaming add-on version 421.1.0.2, 430.1.2.0, and earlier allows remote attackers to run arbitrary OS commands against the system with root privileges.

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 · high confidence

QNAP NAS Media Streaming add-on versions 421.1.0.2, 430.1.2.0 and earlier contains a pre-authentication command injection vulnerability allowing remote attackers to execute arbitrary operating system commands with root privileges.

MitigationUpdate the QNAP Media Streaming add-on to the latest patched version available from QNAP's support portal.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Media Streaming Add OnPlugin / extension
Affected:<= 430.1.2.0<= 421.1.0.2

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Media Streaming add-on is installed
    Log into QNAP admin interface and navigate to App Center or check for Media Streaming add-on in the installed applications list. Alternatively, access the NAS via SSH and list installed QPKG packages using 'sudo /sbin/getcfg QPKG QPKG_Name -f /etc/config/qpkg.conf' or similar QPKG queries.
    Affected if The add-on is present on the system
  2. Identify installed Media Streaming add-on version
    In QNAP App Center, click on the Media Streaming add-on and view its details/version information. Via CLI, check /share/CACHEDEV1_DATA/.qpkg/MediaStreaming or similar QPKG directory for version files, or use 'grep -i version' within the add-on's configuration directory.
    Affected if Version cannot be determined or is at or below 430.1.2.0 or 421.1.0.2
  3. Compare version against affected ranges
    Compare the identified version number to the vulnerable ranges: versions <= 430.1.2.0 and versions <= 421.1.0.2. Note that both 430.x and 421.x branches have separate vulnerable thresholds.
    Affected if Installed version is 430.1.2.0 or lower, OR 421.1.0.2 or lower
  4. Verify remote access to Media Streaming service
    Check if the Media Streaming web interface is accessible externally. Test accessing the streaming portal URL (typically port 8081 or 9000, path /mshare/ or /media/) from the network. Since this is a pre-authentication flaw, external accessibility increases risk.
    Affected if The Media Streaming web service is exposed and reachable from untrusted networks

The system is affected if the QNAP Media Streaming add-on is installed with a version at or below 430.1.2.0 or at or below 421.1.0.2, particularly if the streaming interface is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 430.1.2.0
Interim mitigation

Update the QNAP Media Streaming add-on to the latest patched version available from QNAP's support portal.

Recommended fix Moderate confidence

QNAP Media Streaming add-on version 430.1.2.1 or later (verify latest version at www.qnap.com)

  1. 1. Log in to the QNAP NAS admin interface
  2. 2. Navigate to App Center > Installed Applications
  3. 3. Locate the Media Streaming add-on
  4. 4. Uninstall the current vulnerable version of Media Streaming add-on
  5. 5. Visit the QNAP App Center or QNAP website to download the latest version of Media Streaming add-on
  6. 6. Install the updated Media Streaming add-on version
  7. 7. Verify the installed version matches or exceeds the fixed release version
  8. 8. Restart the Media Streaming service if prompted

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Media Streaming Add On Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-7640 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2017-7640 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