dbcve.org
Music StationApplication · Qnap

CVE-2018-19950

CRITICAL · 9.8 CVSS v3.1 Published 2020-11-02
Fix available
A fix is available. Upgrade to 5.1.13 / 5.2.9 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
If exploited, this command injection vulnerability could allow remote attackers to execute arbitrary commands. This issue affects: QNAP Systems Inc. Music Station versions prior to 5.1.13; versions prior to 5.2.9; versions prior to 5.3.11.

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

Command injection vulnerability in QNAP Music Station web interface allows remote attackers to inject and execute arbitrary OS commands via unspecified input vectors. The flaw is exploitable without authentication given the CVSS 9.8 rating, indicating network-level exploitation with no user interaction required.

MitigationUpdate QNAP Music Station to version 5.1.13, 5.2.9, or 5.3.11 (or later) depending on the firmware branch to patch the command injection flaw.

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
Music StationApplication
Affected:>= 5.3.0, < 5.3.11< 5.1.13>= 5.2.0, < 5.2.9

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.1/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. Verify Music Station is installed
    Log into QNAP QTS as admin, open App Center, and look for Music Station in the installed applications list. Alternatively, access the NAS via SSH and run: /etc/config/qpkg.conf | grep -i music
    Affected if Music Station appears in the installed applications
  2. Identify the Music Station version
    In QTS, go to App Center, right-click Music Station, and select 'Information' to view the version. Or via SSH, check: cat /share/CACHEDEV1_DATA/.qpkg/MusicStation/.qpkg_version 2>/dev/null || cat /mnt/ext/opt/musicstation/.qpkg_version 2>/dev/null
    Affected if The displayed version falls within < 5.1.13, >= 5.2.0 < 5.2.9, or >= 5.3.0 < 5.3.11
  3. Confirm the web interface is accessible
    Attempt to access Music Station web portal at https://[NAS_IP]/musics/ or check if port 80/443 is open and forwarded. In QTS, verify under Control Panel > Security > Service Binding that the web server is enabled.
    Affected if The Music Station web interface is reachable over the network
  4. Look for signs of compromise
    Via SSH, check for suspicious processes: ps aux | grep -E '(nc|bash|sh -i|wget|curl)' and review /var/log/apache2/access_log or /var/log/httpd-access.log for unusual requests to /musics/ endpoints.
    Affected if Unexpected shell processes exist or logs show anomalous Music Station web requests

A user is affected if Music Station is installed, the version is below 5.1.13, between 5.2.0-5.2.9, or between 5.3.0-5.3.11, and the web 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 5.1.13 / 5.2.9 / 5.3.11 or later
Fixed in 5.1.135.2.95.3.11
Interim mitigation

Update QNAP Music Station to version 5.1.13, 5.2.9, or 5.3.11 (or later) depending on the firmware branch to patch the command injection flaw.

Recommended fix High confidence

Music Station 5.3.11 (or later 5.3.x), or 5.2.9 (or later 5.2.x), or 5.1.13 (or later 5.1.x) depending on your current branch

  1. 1. Log in to the QNAP NAS admin interface
  2. 2. Navigate to App Center > Music Station
  3. 3. Check the current installed version of Music Station
  4. 4. If current version is >= 5.3.0 and < 5.3.11, upgrade to version 5.3.11 or later
  5. 5. If current version is >= 5.2.0 and < 5.2.9, upgrade to version 5.2.9 or later
  6. 6. If current version is < 5.1.13, upgrade to version 5.1.13 or later
  7. 7. Alternatively, use QNAP's Control Panel > System > Firmware Update to check for all available updates
  8. 8. Apply the Music Station update and verify successful installation
Caveat Review QNAP release notes for any feature changes between versions; back up configurations before upgrading

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

Fix this in Music Station Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2018-19950 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