LiveActive security incident?Get immediate response
CVE Record

CVE-2017-6200: Sandstorm before build 0.203 allows remote attackers to read any specified file under /etc or /run via the...

Sandstorm before build 0.203 allows remote attackers to read any specified file under /etc or /run via the sandbox backup function. The root cause is that the findFilesToZip function doesn't filter Line Feed (\n) characters in a directory name.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2017-6200 is a Sandstorm file disclosure issue. In builds before 0.203, a remote attacker could abuse the sandbox backup function to read chosen files under /etc or /run, which may expose secrets, configuration, or runtime data.

Executive priority

Prioritize remediation if Sandstorm is used in production or exposed to untrusted users. The impact is sensitive file disclosure, and the fix appears historical, so remaining exposure likely indicates an unmanaged or outdated asset.

Technical view

The issue is in Sandstorm's backup file selection logic. The findFilesToZip function did not filter Line Feed characters in directory names, allowing crafted backup input to include specified files from /etc or /run. The supplied CVE data identifies Sandstorm before build 0.203 as affected.

Likely exposure

Exposure is most likely for organizations still running Sandstorm builds earlier than 0.203. The structured affected-product fields are incomplete, so confirm exposure by checking actual Sandstorm build versions rather than relying on CPE matching.

Exploitation context

The supplied sources do not show KEV listing or active exploitation. Public commits and writeups describe the bug and affected backup path. Treat it as externally relevant where untrusted or remote users can reach Sandstorm backup functionality.

Researcher notes

Evidence is strongest for the root cause, affected version boundary, and file paths at risk. The supplied bundle lacks CVSS, CWE, CPE, and exploitation telemetry, so score and likelihood should be treated as analyst judgment rather than vendor-provided severity.

Mitigation direction

  • Upgrade Sandstorm to build 0.203 or later.
  • Review vendor security guidance and referenced fix commits.
  • Restrict backup functionality to trusted administrators.
  • Audit exposed Sandstorm instances for outdated builds.
  • Review whether /etc or /run secrets were accessible.

Validation and detection

  • Inventory all Sandstorm deployments and record build numbers.
  • Confirm no production instance runs before build 0.203.
  • Review backup-related logs for unusual activity.
  • Check whether sensitive files under /etc or /run contain exposed secrets.
  • Verify access controls around sandbox backup operations.
Prepared
Confidence
medium
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-6200 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.