{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-5217 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-5217 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-5217 is a medium-severity denial of service vulnerability in n/a, published on 9 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-2017-5217 and fix it if it is affected.\n\nWhat it is: CVE-2017-5217 is a medium-severity denial of service vulnerability in n/a, published on 9 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-2017-5217 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-2017-5217/ (Markdown: https://insights.sbomify.com/CVE-2017-5217/index.md)","id":"CVE-2017-5217","markdown":"https://insights.sbomify.com/CVE-2017-5217/index.md","name":"CVE-2017-5217","record":{"aliases":["GHSA-gwv4-rqw3-4w2c"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung Android OS","requires_auth":"none","summary":"A malicious zero-permission app can cause a persistent denial of service on Samsung Android devices by triggering a system_server crash via memory exhaustion during APK parsing.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"samsung_mobile","vendor":"samsung"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"},{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"Installing a zero-permission Android application on certain Samsung Android devices with KK(4.4), L(5.0/5.1), and M(6.0) software can continually crash the system_server process in the Android OS. The zero-permission app will create an active install session for a separate app that it has embedded within it. The active install session of the embedded app is performed using the android.content.pm.PackageInstaller class and its nested classes in the Android API. The active install session will write the embedded APK file to the /data/app directory, but the app will not be installed since third-party applications cannot programmatically install apps. Samsung has modified AOSP in order to accelerate the parsing of APKs by introducing the com.android.server.pm.PackagePrefetcher class and its nested classes. These classes will parse the APKs present in the /data/app directory and other directories, even if the app is not actually installed. The embedded APK that was written to the /data/app directory via the active install session has a very large but valid AndroidManifest.xml file. Specifically, the AndroidManifest.xml file contains a very large string value for the name of a permission-tree that it declares. When system_server tries to parse the APK file of the embedded app from the active install session, it will crash due to an uncaught error (i.e., java.lang.OutOfMemoryError) or an uncaught exception (i.e., std::bad_alloc) because of memory constraints. The Samsung Android device will encounter a soft reboot due to a system_server crash, and this action will keep repeating since parsing the APKs in the /data/app directory as performed by the system_server process is part of the normal boot process. The Samsung ID is SVE-2016-6917.","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":"Denial of service in n/a","id":"CVE-2017-5217","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"SQL injection in n/a","id":"CVE-2017-5218"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2017-5216"},"products":["n/a"],"published":"2017-01-09","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-05","vendors":["n/a"]},"summary":"A malicious zero-permission app can cause a persistent denial of service on Samsung Android devices by triggering a system_server crash via memory exhaustion during APK parsing.","url":"https://insights.sbomify.com/CVE-2017-5217/"}