dbcve.org
QtsOperating system · Qnap

CVE-2013-7174

HIGH · 7.8 CVSS v2.0 Published 2014-01-09
Fix available
A fix is available. Upgrade to after 4.0.3 or later.
See remediation →
87/100
Remediation priority · High
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
Absolute path traversal vulnerability in cgi-bin/jc.cgi in QNAP QTS before 4.1.0 allows remote attackers to read arbitrary files via a full pathname in the f parameter.

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

Absolute path traversal vulnerability in cgi-bin/jc.cgi in QNAP QTS versions prior to 4.1.0 allows remote attackers to read arbitrary files on the system by providing a full pathname in the f parameter, leading to sensitive information disclosure.

MitigationUpgrade QNAP QTS firmware to version 4.1.0 or later to remediate the path traversal vulnerability in jc.cgi; until patched, consider restricting access to the web interface or disabling the affected CGI script.

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.0.3= 4.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
Authentication
None
Confidentiality
Complete
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:C/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. Identify QNAP QTS firmware version
    Access the QNAP admin dashboard and navigate to System Settings > System, or use the QNAP CLI command 'getcfg system version' to determine the installed QTS version
    Affected if Version is 4.0.3 or lower, or is version 4.0 (all versions prior to 4.1.0 are affected)
  2. Confirm jc.cgi is accessible
    Attempt to reach the URI /cgi-bin/jc.cgi on the QNAP device over HTTP or HTTPS
    Affected if The CGI script responds, indicating it is present and enabled
  3. Test f parameter for path traversal
    Send a request to jc.cgi with the f parameter set to a full system path such as /etc/passwd (e.g., /cgi-bin/jc.cgi?f=/etc/passwd)
    Affected if The script returns the contents of the specified file, confirming the path traversal vulnerability is present

The environment is affected if QNAP QTS version is 4.0.3 or lower AND the jc.cgi script is accessible with the f parameter allowing arbitrary file read.

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.

From vendor data
Upgrade available Upgrade to a release after 4.0.3
Interim mitigation

Upgrade QNAP QTS firmware to version 4.1.0 or later to remediate the path traversal vulnerability in jc.cgi; until patched, consider restricting access to the web interface or disabling the affected CGI script.

Fix this in Qts Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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