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

Q: How do I fix CVE-2017-6199?

sandstorm: upgrade to 0.203. Exact commands for each OS are on this page.

Q: Is CVE-2017-6199 being exploited?

CVE-2017-6199 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2017-6199 affect?

CVE-2017-6199 affects sandstorm. Severity is critical (CVSS 9.8). A remote attacker could bypass the Sandstorm organization restriction before build 0.203 via a comma in an email-address field.

Q: How urgent is CVE-2017-6199?

Priority 66/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2017-6199 is a critical-severity flaw (CVSS 9.8) affecting sandstorm. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	3.0% (top 13%)
CISA exploited list	No
Weakness	CWE-287
Published	2018-02-06
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: sandstorm

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-02-06 16:29 UTCPublished CVE record published
2026-06-17 01:21 UTCUpdated Record last modified

sandstorm sandstorm UPGRADE

Affected: < 0.203

Fixed in: 0.203

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy sandstorm || rpm -q sandstorm || sandstorm --version

2. UPGRADE to 0.203 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade sandstorm

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade sandstorm

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-6199?

sandstorm: upgrade to 0.203. Exact commands for each OS are on this page.

Is CVE-2017-6199 being exploited?

CVE-2017-6199 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-6199 affect?

CVE-2017-6199 affects sandstorm. Severity is critical (CVSS 9.8). A remote attacker could bypass the Sandstorm organization restriction before build 0.203 via a comma in an email-address field.

How urgent is CVE-2017-6199?

Priority 66/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2017-6201 HIGH 8.1 UPGRADE A Server Side Request Forgery vulnerability exists in the install app process in Sandstorm before build 0.203
CVE-2017-6200 MEDIUM 6.5 UPGRADE Sandstorm before build 0.203 allows remote attackers to read any specified file under /etc or /run via the san
CVE-2017-6198 MEDIUM 6.5 UPGRADE The Supervisor in Sandstorm doesn't set and enforce the resource limits of a process

References

← Back to latest CVEs