CVE-2016-8358 json
An issue was discovered in Smiths-Medical CADD-Solis Medication Safety Software, Version 1.0; 2.0; 3.0; and 3.1.
published 2017-02-13 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-9206
- cvss
- 8.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
An issue was discovered in Smiths-Medical CADD-Solis Medication Safety Software, Version 1.0; 2.0; 3.0; and 3.1. The affected software does not verify the identities at communication endpoints, which may allow a man-in-the-middle attacker to gain access to the communication channel between endpoints.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSMA-16-306-01 updated cvss 8.5
Smiths Medical CADD-Solis Medication Safety Software Vulnerabilities
-
Smiths Medical CADD-Solis Medication Safety Software 1.0, 2.0, 3.0, 3.1affected: mitigation
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.50% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.5 | CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H |
| NVD | 2.0 | 6.0 | AV:N/AC:M/Au:S/C:P/I:P/A:P |
Affected products
- n/a Smiths-Medical CADD-Solis Medication Safety Software through 3.1
Classification
- Weakness
-
- CWE-346 Origin Validation Error
References
-
ics-cert.us-cert.gov
/advisories/ICSMA-16-306-01
third-party-advisory, us-government-resource
-
securityfocus.com
/bid/94630
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2016-8358
- NVD CVE-2016-8358
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.