dbcve.org
Music StationApplication · Qnap

CVE-2023-23366

MEDIUM · 6.5 CVSS v3.1 Published 2023-10-06
Fix available
A fix is available. Upgrade to 5.3.22 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
A path traversal vulnerability has been reported to affect Music Station. If exploited, the vulnerability could allow authenticated users to read the contents of unexpected files and expose sensitive data via a network. We have already fixed the vulnerability in the following version: Music Station 5.3.22 and later

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

This is a path traversal vulnerability in QNAP Music Station that allows authenticated users to manipulate file path requests using '../' sequences to escape the intended directory and read sensitive files outside the web root. The vulnerability enables unauthorized access to system configuration files, credentials, or other sensitive data via specially crafted HTTP requests.

MitigationUpgrade Music Station to version 5.3.22 or later. As an interim measure, restrict network access to Music Station to trusted users only and monitor logs for unusual file access patterns.

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.22

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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
    Access QNAP QTS Desktop, open App Center, and look for Music Station in the installed applications list. Alternatively, check via QNAP CLI: run 'Container Station' or check '/share/CACHEDEV1_DATA/.qpkg/MusicStation' if SSH access is available.
    Affected if Music Station is present on the QNAP device regardless of version
  2. Determine installed Music Station version
    In QTS App Center, click on Music Station and view the version information displayed, or use QNAP CLI command 'qpkg --get-versions MusicStation' if SSH access is available.
    Affected if Version is greater than or equal to 5.3.0 AND less than 5.3.22
  3. Confirm web interface accessibility
    Attempt to access the Music Station web portal by navigating to 'https://[QNAP-IP]:[PORT]/musicstation/' or check QNAP firewall rules in Control Panel > Security > Firewall to see if port 443/8080 is open to untrusted networks.
    Affected if Music Station web interface is reachable from network segments containing untrusted users
  4. Check for exploitation indicators in logs
    Access QNAP Log Center and filter logs for Music Station. Look for repeated requests containing '../' patterns, access to parent directories like '/etc/', '/root/', or system configuration files outside the Music Station directory.
    Affected if Log entries show directory traversal patterns or unauthorized access to system files from Music Station service accounts

The environment is affected if Music Station version is 5.3.0 through 5.3.21 and the web interface is accessible to untrusted users, or if logs show evidence of traversal attempts.

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.3.22 or later
Fixed in 5.3.22
Interim mitigation

Upgrade Music Station to version 5.3.22 or later. As an interim measure, restrict network access to Music Station to trusted users only and monitor logs for unusual file access patterns.

Recommended fix High confidence

Music Station 5.3.22

  1. 1. Log in to the QNAP NAS admin interface
  2. 2. Navigate to App Center or open Music Station
  3. 3. Check the current installed version of Music Station
  4. 4. If the version is below 5.3.22, look for the Music Station update option
  5. 5. Update Music Station to version 5.3.22 or later
  6. 6. Verify the update was successful by checking the new version number

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

Fix this in Music Station Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-23366 — 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-2023-23366 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