dbcve.org
QtsOperating system · Qnap

CVE-2015-6003

HIGH · 9.3 CVSS v2.0 Published 2015-10-16
Fix available
A fix is available. Upgrade to after 4.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
Directory traversal vulnerability in QNAP QTS before 4.1.4 build 0910 and 4.2.x before 4.2.0 RC2 build 0910, when AFP is enabled, allows remote attackers to read or write to arbitrary files by leveraging access to an OS X (1) user or (2) guest account.

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

Directory traversal vulnerability in QNAP QTS firmware allows remote attackers with access to OS X user or guest accounts to read or write arbitrary files on the NAS device when AFP (Apple Filing Protocol) is enabled. The vulnerability exists in QTS versions before 4.1.4 build 0910 and 4.2.x before 4.2.0 RC2 build 0910.

MitigationUpgrade QNAP QTS to version 4.1.4 build 0910 / 4.2.0 RC2 build 0910 or later. If immediate upgrade is not feasible, disable AFP service if not required, as the vulnerability is only exploitable when AFP is enabled.

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
QtsOperating system
Affected:<= 4.1.4<= 4.2.0

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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. Identify QNAP QTS firmware version
    Log into the QNAP admin interface and navigate to Control Panel > System Settings > Firmware, or run the command 'getsysinfo' via SSH to retrieve the exact QTS version and build number.
    Affected if The installed version is QTS 4.1.4 or earlier, or QTS 4.2.0 RC2 or earlier (any 4.2.x version before build 0910). Compare your version and build number against 4.1.4 build 0910 and 4.2.0 RC2 build 0910.
  2. Confirm AFP service status
    In the QNAP admin interface, go to Control Panel > Network Services > Apple Filing Protocol (AFP), or check via SSH with the command 'ls -la /etc/config/smb.conf' and related AFP configuration files in /share/AFP or similar service directories.
    Affected if AFP is currently enabled on the NAS device.
  3. Verify AFP user accounts exist
    Check for OS X compatible user accounts by reviewing AFP service user access settings in the admin interface under Apple Filing Protocol > Access Control, or list AFP-enabled user accounts via command line if accessible.
    Affected if There are any user accounts (including guest accounts) that have AFP access enabled.
  4. Check for suspicious AFP access logs
    Review QNAP system logs under Log Center for unusual AFP file access patterns, particularly attempts to access paths outside the designated share folders.
    Affected if Log entries show AFP connections accessing paths outside expected share directories, which may indicate exploitation attempts.

You are affected if your QNAP QTS version is 4.1.4 or earlier or 4.2.0 RC2/earlier, AND AFP service is enabled, AND you have OS X or guest user accounts that can access AFP.

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

Upgrade QNAP QTS to version 4.1.4 build 0910 / 4.2.0 RC2 build 0910 or later. If immediate upgrade is not feasible, disable AFP service if not required, as the vulnerability is only exploitable when AFP is enabled.

Recommended fix High confidence

QTS 4.1.4 build 0910 or later; QTS 4.2.0 RC2 build 0910 or later

  1. Log into QNAP QTS admin interface
  2. Navigate to Control Panel > System Settings > Firmware Update
  3. Backup all critical data before proceeding with firmware update
  4. Check current firmware version in System Information > Firmware Version
  5. If running QTS 4.1.x: Upgrade to QTS 4.1.4 build 0910 or later
  6. If running QTS 4.2.x: Upgrade to QTS 4.2.0 RC2 build 0910 or later
  7. After upgrade, verify the new firmware version matches or exceeds the fixed builds
  8. Consider disabling AFP (Apple Filing Protocol) in File Services if not needed, to reduce attack surface
Caveat Standard QNAP firmware update - backup data before proceeding; ensure compatible apps after upgrade

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

Fix this in Qts Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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