CVE-2017-16250

MEDIUMNVD 5.35.3—

5.3

A vulnerability in Mitel ST 14.2, release GA28 and earlier, could allow an attacker to use the API function to enumerate through user-ids which could be used to identify valid user ids and associated user names.

CVSS v3: 5.3
EG Score: 5.3(medium)
EPSS: 46.2%
KEV: Not listed

Published

March 13, 2018

Last Modified

November 21, 2024

References (2)

cve@mitrehttps://www.mitel.com/support/security-advisories/mitel-product-security-advisory-18-0004
af854a3a-2127-422b-91ae-364da2661108https://www.mitel.com/support/security-advisories/mitel-product-security-advisory-18-0004

Weakness Classification(1)

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

CWE-200Exposure of Sensitive Information to an Unauthorized Actor

Data Freshness Timeline

(refreshed 13× 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-06 13:45 UTCepss_batch
2026-06-06 13:45 UTCepss_batch
2026-06-05 22:44 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-04 13:10 UTCepss_batch
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-06-01 13:49 UTCepss_batch
2026-05-31 22:28 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 10:33 UTCEG score recompute
2026-05-28 10:32 UTCGHSA enrichment
2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch

Frequently asked(5)

What is CVE-2017-16250?

CVE-2017-16250 is a medium vulnerability published on March 13, 2018. A vulnerability in Mitel ST 14.2, release GA28 and earlier, could allow an attacker to use the API function to enumerate through user-ids which could be used to identify valid user ids and associated user names.

When was CVE-2017-16250 disclosed?

CVE-2017-16250 was first published in the National Vulnerability Database on March 13, 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-16250 actively exploited?

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

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

CVE-2017-16250 has a CVSS v3 base score of 5.3 (NVD).

How do I remediate CVE-2017-16250?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-16250, 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-16250

Explore →

Is Your Infrastructure Affected by CVE-2017-16250?

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

Start Free Scan →Browse All CVEs

CVE-2017-16250

📅 Published

🔄 Last Modified

🔗 References (2)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2017-16250?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (2)

Frequently asked(5)

Related CVEs(same CWE)