CVE-2013-6955
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 · uneditedwebman/imageSelector.cgi in Synology DiskStation Manager (DSM) 4.0 before 4.0-2259, 4.2 before 4.2-3243, and 4.3 before 4.3-3810 Update 1 allows remote attackers to append data to arbitrary files, and consequently execute arbitrary code, via a pathname in the SLICEUPLOAD X-TMP-FILE HTTP header.
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 confidenceA path traversal and file injection vulnerability in webman/imageSelector.cgi allows remote unauthenticated attackers to control the X-TMP-FILE HTTP header to append malicious data to arbitrary files on the Synology NAS filesystem, leading to arbitrary code execution.
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= 4.0= 4.2= 4.3= 4.3-3810CVSS 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
- Complete
- Availability
- Complete
AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify DSM versionLog into Synology DSM admin console and go to Control Panel > System > Update & Restore, or run 'grep -i version /etc/VERSION' via SSH to retrieve the installed DSM version numberAffected if The installed version is 4.0, 4.2, or 4.3-3810 (any build before the fixed updates)
-
Verify webman module is installedCheck for the presence of /webman/imageSelector.cgi on the NAS by attempting to access https://[nas-ip]/imageSelector.cgi or checking file existence via SSH at /usr/syno/synoman/webman/cgi/imageSelector.cgiAffected if The imageSelector.cgi file exists in the webman directory and responds to requests
-
Confirm web interface accessibilityAttempt an HTTP request to the Synology IP on port 5000 or 5001 to verify the DSM web interface is reachable from the networkAffected if The DSM web interface is accessible from untrusted networks without restriction
-
Check X-TMP-FILE header handlingSend a test HTTP request to imageSelector.cgi with a modified X-TMP-FILE header (e.g., X-TMP-FILE: /etc/passwd) using curl -H 'X-TMP-FILE: /etc/passwd' http://[nas-ip]/webman/imageSelector.cgi - observe if the server accepts and processes the headerAffected if The server accepts arbitrary paths in the X-TMP-FILE header without rejecting or sanitizing the input
The environment is affected if the Synology DSM version is 4.0, 4.2, or 4.3-3810 AND the webman/imageSelector.cgi endpoint is network-accessible, allowing an attacker to manipulate the X-TMP-FILE header for file injection.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Synology DSM to version 4.0-2259, 4.2-3243, or 4.3-3810 Update 1 or later. If patching is not feasible immediately, disable or restrict access to the webman interface and imageSelector.cgi through firewall rules or network segmentation.
DSM 4.0-2259, DSM 4.2-3243, or DSM 4.3-3810 Update 1 (or later) depending on the current major version branch
- 1. Back up all critical data on the Synology NAS before proceeding with any system upgrade.
- 2. Identify the current DSM version installed on the DiskStation Manager.
- 3. For DSM 4.0: Upgrade to version 4.0-2259 or later.
- 4. For DSM 4.2: Upgrade to version 4.2-3243 or later.
- 5. For DSM 4.3: Upgrade to version 4.3-3810 Update 1 or later.
- 6. Download the appropriate DSM update from the official Synology download center at https://www.synology.com/en-global/support/download.
- 7. Install the update via DSM Control Panel > Update & Restore > DSM Update, or manually apply the .pat file if the automatic update is not available.
- 8. After upgrading, verify that the webman/imageSelector.cgi vulnerability is no longer present by confirming the DSM version and checking that the security fix is applied.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6955 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-6955 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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