CVE-2016-8358
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe CADD-Solis Medication Safety Software fails to verify identities at communication endpoints, allowing attackers to intercept or manipulate data in transit via man-in-the-middle attacks. This is a fundamental lack of mutual authentication in the communication layer.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0= 2.0= 3.0= 3.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify CADD-Solis software installationCheck system inventory or installed programs for Smiths Medical Cadd Solis Medication Safety SoftwareAffected if Software is present on the system
-
Determine installed versionUse system inventory tools, registry queries, or application about/help menus to find the exact version number of the CADD-Solis softwareAffected if Version is 1.0, 2.0, 3.0, or 3.1
-
Verify mutual authentication configurationInspect communication settings, network configuration files, or application security settings to determine if mutual TLS (mTLS) or certificate-based authentication is enabled between communication endpointsAffected if Mutual authentication is not configured or disabled for data exchange channels
-
Check communication channel securityReview network logs, SSL/TLS inspection, or configuration files to verify that all communication endpoints verify each other's identities before allowing data transferAffected if Endpoints do not verify mutual identity (only server authentication or no authentication is configured)
A system is affected if CADD Solis software versions 1.0 through 3.1 are installed and the communication layer lacks mutual authentication between endpoints.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement mutual TLS (mTLS) or certificate-based authentication to verify the identity of all communication endpoints before allowing data exchange.
- Consultation12.0 h
- Implementation40.0 h
- Testing32.0 h
- Review / QA16.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $27,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-8358 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-8358 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data