CVE-2017-14013 json
A Client-Side Enforcement of Server-Side Security issue was discovered in ProMinent MultiFLEX M10a Controller web interface.
published 2017-10-17 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-5528
- cvss
- 5.6
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 60%
- public exploits
- 0
- none known
Summary
A Client-Side Enforcement of Server-Side Security issue was discovered in ProMinent MultiFLEX M10a Controller web interface. The log out function in the application removes the user's session only on the client side. This may allow an attacker to bypass protection mechanisms, gain privileges, or assume the identity of an authenticated user.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-17-285-01 updated cvss 5.6
ProMinent MultiFLEX M10a Controller
-
ProMinent MultiFLEX M10a Controller web interfaceaffected: mitigation “ProMinent has not provided mitigations for these vulnerabilities.”
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
Exploit prediction
0.93% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.6 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected products
- n/a ProMinent MultiFLEX M10a Controller
Classification
References
-
securityfocus.com
/bid/101259
vdb-entry, third-party-advisory
-
ics-cert.us-cert.gov
/advisories/ICSA-17-285-01
mitigation, third-party-advisory, us-government-resource
Sources
- CVE List CVE-2017-14013
- NVD CVE-2017-14013
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.