{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-6527 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-6527 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-6527 is a high-severity unsafe deserialization vulnerability in n/a, published on 18 Jan 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2016-6527 and fix it if it is affected.\n\nWhat it is: CVE-2016-6527 is a high-severity unsafe deserialization vulnerability in n/a, published on 18 Jan 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2016-6527 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2016-6527/ (Markdown: https://insights.sbomify.com/CVE-2016-6527/index.md)","id":"CVE-2016-6527","markdown":"https://insights.sbomify.com/CVE-2016-6527/index.md","name":"CVE-2016-6527","record":{"aliases":["GHSA-c2pp-vm7c-3r42"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["denial_of_service","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung Telecom app","requires_auth":"none","summary":"Attackers can cause crashes or gain privileges in Samsung Telecom app via malformed serializable objects in SmartCall Activity.","user_interaction":"required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"samsung_mobile","vendor":"samsung"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"The SmartCall Activity component in Telecom application on Samsung Note device L(5.0/5.1) and M(6.0) allows attackers to cause a denial of service (crash and reboot) or possibly gain privileges via a malformed serializable object.","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":"Deserialization in n/a","id":"CVE-2016-6527","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2016"},"n_packages":0,"n_references":3,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2016-6530"},"packages":[],"prev":{"headline":"Deserialization in n/a","id":"CVE-2016-6526"},"products":["n/a"],"published":"2017-01-18","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-9139","kev_date_added":null,"published":"2018-03-30"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-9143","kev_date_added":null,"published":"2018-03-30"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-5538","kev_date_added":null,"published":"2017-03-23"},{"cvss_score":9.8,"headline":"Denial of service in n/a","id":"CVE-2016-9965","kev_date_added":null,"published":"2016-12-16"},{"cvss_score":9.8,"headline":"Denial of service in n/a","id":"CVE-2016-9966","kev_date_added":null,"published":"2016-12-16"},{"cvss_score":9.8,"headline":"Denial of service in n/a","id":"CVE-2016-9967","kev_date_added":null,"published":"2016-12-16"},{"cvss_score":8.4,"headline":"Memory corruption in n/a","id":"CVE-2017-18020","kev_date_added":null,"published":"2018-01-04"}],"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-06","vendors":["n/a"]},"summary":"Attackers can cause crashes or gain privileges in Samsung Telecom app via malformed serializable objects in SmartCall Activity.","url":"https://insights.sbomify.com/CVE-2016-6527/"}