dbcve.org
Nas Proxy ServerApplication · Qnap

CVE-2017-7637

CRITICAL · 9.8 CVSS v3.0 Published 2018-06-05
Fix available
A fix is available. Upgrade to 1.3.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 Proxy Server through version 1.2.0 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 Proxy Server through version 1.2.0 contains a pre-authentication remote code execution vulnerability allowing unauthenticated remote attackers to execute arbitrary operating system commands with root privileges. The CVSS 9.8 score reflects the critical severity of complete system compromise via easily exploitable command injection.

MitigationImmediately update Proxy Server to a patched version if available, or disable/uninstall the vulnerable application until a patch is released. Restrict network access to the NAS management interfaces as an interim control.

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
Nas Proxy ServerApplication
Affected:< 1.3.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
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 Proxy Server application is installed
    Access the QNAP NAS web interface and navigate to App Center or Application Management to verify if the Proxy Server application is listed as installed. Alternatively, access the NAS via SSH and list installed QNAP packages using the package management commands available on the device.
    Affected if Proxy Server appears in the list of installed applications
  2. Locate the installed Proxy Server version
    In the QNAP web interface, go to the Proxy Server application settings or about page to view the current version number. If using SSH, look for version information in the application directory or configuration files typically stored under /share/ or /opt/ for third-party apps.
    Affected if The version displayed is less than 1.3.0 or the version cannot be determined (indicating an old installation)
  3. Verify the service is enabled and running
    Check the Proxy Server status in the QNAP web interface under Application Manager or via SSH by checking running processes related to proxy or the specific service name used by this application.
    Affected if The Proxy Server service shows as running or enabled

If Proxy Server is installed and the discovered version is below 1.3.0, the system is vulnerable to pre-authentication remote code execution.

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 1.3.0 or later
Fixed in 1.3.0
Interim mitigation

Immediately update Proxy Server to a patched version if available, or disable/uninstall the vulnerable application until a patch is released. Restrict network access to the NAS management interfaces as an interim control.

Recommended fix High confidence

Proxy Server version 1.3.0 or later

  1. Log into the QNAP NAS administration interface
  2. Navigate to the App Center or Proxy Server application settings
  3. Locate the Proxy Server application
  4. Check the current installed version to confirm it is below 1.3.0
  5. Update the Proxy Server application to version 1.3.0 or the latest available version from QNAP
  6. After update, verify the new version is running in the application management area
  7. Review Proxy Server configuration settings to ensure they are as expected after the update

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

Fix this in Nas Proxy Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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