dbcve.org
Syncthru 6Application · Samsung

CVE-2015-5473

CRITICAL · 9.8 CVSS v3.0 Published 2017-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Multiple directory traversal vulnerabilities in Samsung SyncThru 6 before 1.0 allow remote attackers to delete arbitrary files via unspecified parameters to (1) upload/updateDriver or (2) upload/addDriver or to execute arbitrary code with SYSTEM privileges via unspecified parameters to (3) uploadCloning.html, (4) fileupload.html, (5) uploadFirmware.html, or (6) upload/driver.

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

Samsung SyncThru 6 before version 1.0 contains multiple directory traversal vulnerabilities in its web interface. Attackers can exploit six different upload endpoints (upload/updateDriver, upload/addDriver, uploadCloning.html, fileupload.html, uploadFirmware.html, upload/driver) to either delete arbitrary files or execute arbitrary code with SYSTEM privileges by manipulating unspecified parameters to traverse directory paths.

MitigationApply the vendor patch (Samsung SyncThru 6 version 1.0 or later) to remediate the directory traversal vulnerabilities. If immediate patching is not feasible, restrict network access to the SyncThru web interface using firewall rules or network segmentation to reduce exposure.

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
Syncthru 6Application
Affected:<= -

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 Samsung SyncThru 6 is installed
    Access the device web interface or check system information to identify if the product is Samsung SyncThru 6. Look for 'SyncThru' branding or check the device model information.
    Affected if The device is running Samsung SyncThru 6 web interface
  2. Check the installed version
    Locate the version information within the SyncThru web interface (typically in 'Settings' > 'General' or 'About' section) or check the firmware/version displayed on the device. Compare this version against version 1.0.
    Affected if The installed version is any version prior to 1.0 (versions like 0.x, 1.0-beta, or unpatched versions)
  3. Verify the web interface is accessible
    Attempt to access the SyncThru web interface via HTTP/HTTPS on the device's IP address. Confirm the upload endpoints are reachable.
    Affected if The web interface and upload endpoints (upload/updateDriver, upload/addDriver, uploadCloning.html, fileupload.html, uploadFirmware.html, upload/driver) are accessible over the network
  4. Inspect upload functionality for directory traversal protection
    If safe to test in an isolated environment, examine whether the upload functionality properly sanitizes path traversal sequences (..) in file upload parameters. Check if arbitrary directory paths can be specified in upload forms.
    Affected if The upload endpoints do not properly validate or sanitize path traversal characters in upload parameters

You are affected if the device runs Samsung SyncThru 6 with a version lower than 1.0 and the web interface with its upload endpoints is network-accessible.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch (Samsung SyncThru 6 version 1.0 or later) to remediate the directory traversal vulnerabilities. If immediate patching is not feasible, restrict network access to the SyncThru web interface using firewall rules or network segmentation to reduce exposure.

Fix this in Syncthru 6 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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