{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-3218 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-3218 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-3218 is a high-severity vulnerability in Samsung Magician, published on 21 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-3218 and fix it if it is affected.\n\nWhat it is: CVE-2017-3218 is a high-severity vulnerability in Samsung Magician, published on 21 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-3218 in the wild and no public exploit code.\n\nAffected product: Samsung Magician. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-3218/ (Markdown: https://insights.sbomify.com/CVE-2017-3218/index.md)","id":"CVE-2017-3218","markdown":"https://insights.sbomify.com/CVE-2017-3218/index.md","name":"CVE-2017-3218","record":{"aliases":["GHSA-7xpm-33wp-wg2w"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung Magician","requires_auth":"none","summary":"Attackers can intercept update traffic due to missing TLS validation, potentially delivering malicious updates to Samsung Magician users.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"certcc","cpe":[{"product":"magician","vendor":"samsung"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"},{"id":"CWE-311","name":"Missing Encryption of Sensitive Data"},{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Security feature bypass in Magician","id":"CVE-2017-3218","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Supply chain in True Image","id":"CVE-2017-3219"},"packages":[],"prev":{"headline":"Missing authorization in LMU 3030 OBD-II","id":"CVE-2017-3217"},"products":["Magician"],"published":"2017-06-21","related":[{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2025-57836","kev_date_added":null,"published":"2026-01-05"},{"cvss_score":7.3,"headline":"Information disclosure in n/a","id":"CVE-2024-23769","kev_date_added":null,"published":"2024-02-07"},{"cvss_score":6.7,"headline":"Path traversal in n/a","id":"CVE-2024-31952","kev_date_added":null,"published":"2024-05-09"},{"cvss_score":6.7,"headline":"Privilege escalation in n/a","id":"CVE-2024-31953","kev_date_added":null,"published":"2024-05-09"},{"cvss_score":6.3,"headline":"Privilege escalation in n/a","id":"CVE-2024-36071","kev_date_added":null,"published":"2024-06-20"},{"cvss_score":5.3,"headline":"Privilege escalation in n/a","id":"CVE-2025-32098","kev_date_added":null,"published":"2025-09-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["Samsung"]},"summary":"Attackers can intercept update traffic due to missing TLS validation, potentially delivering malicious updates to Samsung Magician users.","url":"https://insights.sbomify.com/CVE-2017-3218/"}