CVE-2017-3218
First published: Wed Jun 21 2017(Updated: )
Samsung Magician 5.0 fails to validate TLS certificates for HTTPS software update traffic. Prior to version 5.0, Samsung Magician uses HTTP for software updates.
Credit: cret@cert.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Samsung Magician | =5.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2017-3218?
CVE-2017-3218 has been classified as a medium severity vulnerability.
How do I fix CVE-2017-3218?
To fix CVE-2017-3218, upgrade Samsung Magician to a version higher than 5.0 that validates TLS certificates.
What is the impact of CVE-2017-3218?
The impact of CVE-2017-3218 allows attackers to perform man-in-the-middle attacks on software update traffic.
How can I mitigate CVE-2017-3218 if I cannot update?
If unable to update, consider disabling the software update feature in Samsung Magician to mitigate risks associated with CVE-2017-3218.
Is CVE-2017-3218 still exploitable in later versions?
CVE-2017-3218 is not exploitable in versions of Samsung Magician released after 5.0 that implement proper TLS certificate validation.
- collector/nvd-index
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/severity
- agent/last-modified-date
- agent/author
- agent/tags
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- vendor/samsung
- canonical/samsung magician
- version/samsung magician/5.0