CVE-2014-0357 json
Amtelco miSecureMessages allows remote attackers to read the messages of arbitrary users via an XML request containing a valid license key…
published 12y ago modified 4mo ago also EUVD-2014-0395
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 79%
- public exploits
- 0
- none known
Summary
Amtelco miSecureMessages allows remote attackers to read the messages of arbitrary users via an XML request containing a valid license key and a modified contactID value, as demonstrated by a request from the iOS or Android application.
Is CVE-2014-0357 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-14-121-01 updated cvss 7.0
AMTELCO miSecure Vulnerabilities
-
AMTELCO miSecureMessages (to include Android, iPhone, and Blackberry mobile device applications) 6.2affected: mitigation “AMTELCO has developed an update, Version 6.3, that resolves 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
1.83% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
kb.cert.org
/vuls/id/251628
third-party-advisory, us-government-resource
-
ics-cert.us-cert.gov
/advisories/ICSA-14-121-01
us-government-resource
- service.amtelco.com /INFINITY/MSM/MSM6.2SecurityBriefing.pdf
Sources
- CVE List CVE-2014-0357
- NVD CVE-2014-0357
Fencer Intel 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.