CVE-2017-6199

Public Exploit

Description

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

Category

9.8
CVSS
Severity: Critical
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.08%
Vendor Advisory sandstorm.io
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://github.com/sandstorm-io/sandstorm/commit/37bd9a7f4eb776cdc2d3615f0bfea1254b66f59d third party advisory patch
https://github.com/sandstorm-io/sandstorm/blob/v0.202/shell/packages/sandstorm-db/db.js#L1112 third party advisory
https://sandstorm.io/news/2017-03-02-security-review vendor advisory
https://devco.re/blog/2018/01/26/Sandstorm-Security-Review-CVE-2017-6200-en/ third party advisory exploit

Frequently Asked Questions

What is the severity of CVE-2017-6199?
CVE-2017-6199 has been scored as a critical severity vulnerability.
How to fix CVE-2017-6199?
To fix CVE-2017-6199, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-6199 being actively exploited in the wild?
It is possible that CVE-2017-6199 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.