{"answers":{"affected":"It affects 9 products.","exploited":"There is no known exploitation of CVE-2016-10409 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-10409 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-10409 is a high-severity 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-10409 and fix it if it is affected.\n\nWhat it is: CVE-2016-10409 is a high-severity 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-10409 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-10409/ (Markdown: https://insights.sbomify.com/CVE-2016-10409/index.md)","id":"CVE-2016-10409","markdown":"https://insights.sbomify.com/CVE-2016-10409/index.md","name":"CVE-2016-10409","record":{"aliases":["GHSA-mcfr-36hc-hjp6"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Qualcomm Snapdragon firmware","requires_auth":"none","summary":"A time-of-check time-of-use race condition in Qualcomm Snapdragon firmware allows attackers to manipulate RPMB requests, potentially leading to privilege escalation or data modification.","user_interaction":"not_required","vuln_class":"race_condition"},"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"},{"product":"sd_650_firmware","vendor":"qualcomm"},{"product":"sd_652_firmware","vendor":"qualcomm"},{"product":"sd_820_firmware","vendor":"qualcomm"},{"product":"sd_820a_firmware","vendor":"qualcomm"},{"product":"sd_835_firmware","vendor":"qualcomm"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile and Snapdragon Mobile SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 820, SD 820A, and SD 835, TOCTOU vulnerability may occur while composing the RPMB request using HLOS controlled buffers.","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":"Race condition in Snapdragon Automobile, Snapdragon Mobile","id":"CVE-2016-10409","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","qualcomm:sd_650_firmware","qualcomm:sd_652_firmware","qualcomm:sd_820_firmware","qualcomm:sd_820a_firmware","qualcomm:sd_835_firmware"],"type":"race_condition","year":"2016"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2016-10410"},"packages":[],"prev":{"headline":"Improper Access Control in Core.","id":"CVE-2016-10408"},"products":["Snapdragon Automobile, 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":"Memory corruption in Snapdragon Mobile","id":"CVE-2016-10454","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"}],"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":"A time-of-check time-of-use race condition in Qualcomm Snapdragon firmware allows attackers to manipulate RPMB requests, potentially leading to privilege escalation or data modification.","url":"https://insights.sbomify.com/CVE-2016-10409/"}