{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2016-10454 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-10454 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-10454 is a critical memory corruption vulnerability in Qualcomm Sd 425 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-10454 and fix it if it is affected.\n\nWhat it is: CVE-2016-10454 is a critical memory corruption vulnerability in Qualcomm Sd 425 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-10454 in the wild and no public exploit code.\n\nAffected product: Qualcomm Sd 425 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-10454/ (Markdown: https://insights.sbomify.com/CVE-2016-10454/index.md)","id":"CVE-2016-10454","markdown":"https://insights.sbomify.com/CVE-2016-10454/index.md","name":"CVE-2016-10454","record":{"aliases":["GHSA-3g28-v7g2-x3c3"],"analysis":{"component_type":"hardware_firmware","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 index in a QTEE API function allows attackers to potentially execute code or escalate privileges on affected Qualcomm Snapdragon devices.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"qualcomm","cpe":[{"product":"sd_425_firmware","vendor":"qualcomm"},{"product":"sd_430_firmware","vendor":"qualcomm"},{"product":"sd_450_firmware","vendor":"qualcomm"},{"product":"sd_625_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-129","name":"Improper Validation of Array Index"}],"description":"In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile SD 425, SD 430, SD 450, and SD 625, in a QTEE API function, an array out-of-bounds index can occur.","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-10454","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"qualcomm:sd_425_firmware","products":["qualcomm:sd_425_firmware","qualcomm:sd_430_firmware","qualcomm:sd_450_firmware","qualcomm:sd_625_firmware"],"type":"memory_corruption","year":"2016"},"n_packages":0,"n_references":2,"next":{"headline":"Null dereference in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2016-10455"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2016-10453"},"products":["Snapdragon Mobile"],"published":"2018-04-18","related":[{"cvss_score":9.8,"headline":"Missing authorization in Snapdragon Automobile, Snapdragon Mobile","id":"CVE-2015-9110","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Null dereference in Snapdragon Automobile, Snapdragon Mobile","id":"CVE-2015-9114","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Information disclosure in Snapdragon Automobile, Snapdragon Mobile","id":"CVE-2016-10430","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Missing authorization in Snapdragon Mobile","id":"CVE-2016-10440","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Security feature bypass in Snapdragon Automobile, Snapdragon Mobile","id":"CVE-2016-10471","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":8.1,"headline":"Race condition in Snapdragon Automobile, Snapdragon Mobile","id":"CVE-2016-10409","kev_date_added":null,"published":"2018-04-18"}],"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-16","vendors":["Qualcomm, Inc."]},"summary":"An out-of-bounds index in a QTEE API function allows attackers to potentially execute code or escalate privileges on affected Qualcomm Snapdragon devices.","url":"https://insights.sbomify.com/CVE-2016-10454/"}