CVE-2017-6199

CRITICALNVD 9.89.8—

9.8

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

CVSS v3: 9.8
EG Score: 9.8(medium)
EPSS: 34.0%
KEV: Not listed

Published

February 6, 2018

Last Modified

November 21, 2024

References (8)

cve@mitrehttps://devco.re/blog/2018/01/26/Sandstorm-Security-Review-CVE-2017-6200-en/
cve@mitrehttps://github.com/sandstorm-io/sandstorm/blob/v0.202/shell/packages/sandstorm-db/db.js#L1112
cve@mitrehttps://github.com/sandstorm-io/sandstorm/commit/37bd9a7f4eb776cdc2d3615f0bfea1254b66f59d
cve@mitrehttps://sandstorm.io/news/2017-03-02-security-review
af854a3a-2127-422b-91ae-364da2661108https://devco.re/blog/2018/01/26/Sandstorm-Security-Review-CVE-2017-6200-en/
af854a3a-2127-422b-91ae-364da2661108https://github.com/sandstorm-io/sandstorm/blob/v0.202/shell/packages/sandstorm-db/db.js#L1112
af854a3a-2127-422b-91ae-364da2661108https://github.com/sandstorm-io/sandstorm/commit/37bd9a7f4eb776cdc2d3615f0bfea1254b66f59d
af854a3a-2127-422b-91ae-364da2661108https://sandstorm.io/news/2017-03-02-security-review

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-287Improper Authentication

Data Freshness Timeline

(refreshed 9× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-04 13:10 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 11:52 UTCEG score recompute
2026-05-28 11:52 UTCGHSA enrichment
2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 17:01 UTCOSV refresh
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch

Frequently asked(5)

What is CVE-2017-6199?

CVE-2017-6199 is a critical vulnerability published on February 6, 2018. A remote attacker could bypass the Sandstorm organization restriction before build 0.203 via a comma in an email-address field.

When was CVE-2017-6199 disclosed?

CVE-2017-6199 was first published in the National Vulnerability Database on February 6, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2017-6199 actively exploited?

CVE-2017-6199 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 34.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2017-6199?

CVE-2017-6199 has a CVSS v3 base score of 9.8 (NVD).

How do I remediate CVE-2017-6199?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-6199, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-6199

Explore →

Is Your Infrastructure Affected by CVE-2017-6199?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2017-6199

📅 Published

🔄 Last Modified

🔗 References (8)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2017-6199?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (8)

Frequently asked(5)

Related CVEs(same CWE)