LiveActive security incident?Get immediate response
CVE Record

CVE-2017-6199: A remote attacker could bypass the Sandstorm organization restriction before build 0.203 via a comma in an...

A remote attacker could bypass the Sandstorm organization restriction before build 0.203 via a comma in an email-address field.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2017-6199 is an access-control weakness in Sandstorm before build 0.203. A remote user could bypass an organization restriction by placing a comma in an email-address field. The practical concern is unauthorized access to a Sandstorm instance intended to be limited to approved organizational users.

Executive priority

Treat as a targeted access-control cleanup item. Prioritize quickly for internet-facing Sandstorm instances or environments relying on organization restrictions to protect internal applications or data.

Technical view

The issue concerns Sandstorm's organization restriction logic before build 0.203. Source material describes a parsing/validation flaw involving comma-containing email-address fields. The available record does not provide CVSS, CWE, detailed affected CPEs, or exploit telemetry.

Likely exposure

Exposure is likely limited to Sandstorm deployments running builds before 0.203 with organization-based access restrictions enabled. Publicly reachable instances have higher business relevance because the described attacker is remote.

Exploitation context

The provided sources do not show known active exploitation, and the CVE is not listed as KEV. The public description indicates remote bypass potential, but does not provide exploit maturity, prevalence, or real-world incident evidence.

Researcher notes

Evidence is sparse but consistent: the CVE description and referenced Sandstorm commit indicate a pre-0.203 organization restriction bypass tied to comma handling in email fields. Avoid assuming broader product impact beyond Sandstorm without vendor evidence.

Mitigation direction

  • Upgrade Sandstorm to build 0.203 or later.
  • Review Sandstorm vendor guidance and the referenced fixing commit.
  • Confirm organization restriction settings match intended access policy.
  • Audit existing accounts for suspicious or malformed email-address values.

Validation and detection

  • Identify any Sandstorm instances and record their build versions.
  • Flag deployments running builds earlier than 0.203.
  • Check whether organization restrictions are enabled on those deployments.
  • Review account records for comma-containing email-address fields.
  • Confirm tests cover comma handling in email-address validation.
Prepared
Confidence
medium
Sources
6

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-6199 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
5Source 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.