{"answers":{"affected":"It affects 18 products.","exploited":"There is no known exploitation of CVE-2016-10479 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-10479 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-10479 is a critical memory corruption vulnerability in Qualcomm Mdm9607 Firmware, published on 18 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-10479 and fix it if it is affected.\n\nWhat it is: CVE-2016-10479 is a critical memory corruption vulnerability in Qualcomm Mdm9607 Firmware, published on 18 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2016-10479 in the wild and no public exploit code.\n\nAffected product: Qualcomm Mdm9607 Firmware. 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-10479/ (Markdown: https://insights.sbomify.com/CVE-2016-10479/index.md)","id":"CVE-2016-10479","markdown":"https://insights.sbomify.com/CVE-2016-10479/index.md","name":"CVE-2016-10479","record":{"aliases":["GHSA-8x3j-3wrm-mfpp"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Qualcomm Snapdragon Mobile","requires_auth":"none","summary":"An out-of-bounds write in the QMI Proxy allows attackers to execute arbitrary code or escalate privileges on affected Android devices.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"qualcomm","cpe":[{"product":"mdm9607_firmware","vendor":"qualcomm"},{"product":"mdm9615_firmware","vendor":"qualcomm"},{"product":"mdm9635m_firmware","vendor":"qualcomm"},{"product":"mdm9640_firmware","vendor":"qualcomm"},{"product":"sd_205_firmware","vendor":"qualcomm"},{"product":"sd_210_firmware","vendor":"qualcomm"},{"product":"sd_212_firmware","vendor":"qualcomm"},{"product":"sd_400_firmware","vendor":"qualcomm"},{"product":"sd_415_firmware","vendor":"qualcomm"},{"product":"sd_600_firmware","vendor":"qualcomm"},{"product":"sd_615_firmware","vendor":"qualcomm"},{"product":"sd_616_firmware","vendor":"qualcomm"},{"product":"sd_617_firmware","vendor":"qualcomm"},{"product":"sd_650_firmware","vendor":"qualcomm"},{"product":"sd_652_firmware","vendor":"qualcomm"},{"product":"sd_800_firmware","vendor":"qualcomm"},{"product":"sd_810_firmware","vendor":"qualcomm"},{"product":"sd_820_firmware","vendor":"qualcomm"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile MDM9607, MDM9615, MDM9635M, MDM9640, SD 210/SD 212/SD 205, SD 400, SD 600, SD 615/16/SD 415, SD 617, SD 650/52, SD 800, SD 810, and SD 820, an arbitrary length value from an incoming message to QMI Proxy can lead to an out-of-bounds write in the stack variable message.","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":"Memory corruption in Snapdragon Mobile","id":"CVE-2016-10479","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"qualcomm:mdm9607_firmware","products":["qualcomm:mdm9607_firmware","qualcomm:mdm9615_firmware","qualcomm:mdm9635m_firmware","qualcomm:mdm9640_firmware","qualcomm:sd_205_firmware","qualcomm:sd_210_firmware","qualcomm:sd_212_firmware","qualcomm:sd_400_firmware","qualcomm:sd_415_firmware","qualcomm:sd_600_firmware","qualcomm:sd_615_firmware","qualcomm:sd_616_firmware","qualcomm:sd_617_firmware","qualcomm:sd_650_firmware","qualcomm:sd_652_firmware","qualcomm:sd_800_firmware","qualcomm:sd_810_firmware","qualcomm:sd_820_firmware"],"type":"memory_corruption","year":"2016"},"n_packages":0,"n_references":2,"next":{"headline":"Integer overflow in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2016-10480"},"packages":[],"prev":{"headline":"Integer overflow in Snapdragon Mobile","id":"CVE-2016-10478"},"products":["Snapdragon Mobile"],"published":"2018-04-18","related":[{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Auto, Snapdragon Mobile, Snapdragon Wearables","id":"CVE-2019-10531","kev_date_added":null,"published":"2019-11-06"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Voice \u0026 Music","id":"CVE-2019-2276","kev_date_added":null,"published":"2019-07-25"},{"cvss_score":9.8,"headline":"Denial of service in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear","id":"CVE-2018-5915","kev_date_added":null,"published":"2019-01-18"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2015-9126","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Null dereference in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2016-10481","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Denial of service in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2017-18074","kev_date_added":null,"published":"2018-04-11"}],"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-09-17","vendors":["Qualcomm, Inc."]},"summary":"An out-of-bounds write in the QMI Proxy allows attackers to execute arbitrary code or escalate privileges on affected Android devices.","url":"https://insights.sbomify.com/CVE-2016-10479/"}