{"answers":{"affected":"It affects 19 products.","exploited":"There is no known exploitation of CVE-2016-10406 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-10406 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-10406 is a high-severity vulnerability in Qualcomm Mdm9650 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-10406 and fix it if it is affected.\n\nWhat it is: CVE-2016-10406 is a high-severity vulnerability in Qualcomm Mdm9650 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-10406 in the wild and no public exploit code.\n\nAffected product: Qualcomm Mdm9650 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-10406/ (Markdown: https://insights.sbomify.com/CVE-2016-10406/index.md)","id":"CVE-2016-10406","markdown":"https://insights.sbomify.com/CVE-2016-10406/index.md","name":"CVE-2016-10406","record":{"aliases":["GHSA-j5xp-cqqg-c5jq"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Qualcomm Snapdragon firmware","requires_auth":"none","summary":"An attacker can read kernel memory addresses via debug logs in Qualcomm Snapdragon firmware, bypassing kptr_restrict protections.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"qualcomm","cpe":[{"product":"mdm9650_firmware","vendor":"qualcomm"},{"product":"sd_205_firmware","vendor":"qualcomm"},{"product":"sd_210_firmware","vendor":"qualcomm"},{"product":"sd_212_firmware","vendor":"qualcomm"},{"product":"sd_410_firmware","vendor":"qualcomm"},{"product":"sd_412_firmware","vendor":"qualcomm"},{"product":"sd_415_firmware","vendor":"qualcomm"},{"product":"sd_430_firmware","vendor":"qualcomm"},{"product":"sd_450_firmware","vendor":"qualcomm"},{"product":"sd_615_firmware","vendor":"qualcomm"},{"product":"sd_616_firmware","vendor":"qualcomm"},{"product":"sd_617_firmware","vendor":"qualcomm"},{"product":"sd_625_firmware","vendor":"qualcomm"},{"product":"sd_650_firmware","vendor":"qualcomm"},{"product":"sd_652_firmware","vendor":"qualcomm"},{"product":"sd_808_firmware","vendor":"qualcomm"},{"product":"sd_810_firmware","vendor":"qualcomm"},{"product":"sd_820_firmware","vendor":"qualcomm"},{"product":"sd_835_firmware","vendor":"qualcomm"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile MDM9650, SD 210/SD 212/SD 205, SD 410/12, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 808, SD 810, SD 820, and SD 835, while printing debug message of a pointer in wlan_qmi_err_cb, the real kernel address will be printed regardless of the kptr_restrict system settings.","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":"Information disclosure in Snapdragon Mobile","id":"CVE-2016-10406","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"qualcomm:mdm9650_firmware","products":["qualcomm:mdm9650_firmware","qualcomm:sd_205_firmware","qualcomm:sd_210_firmware","qualcomm:sd_212_firmware","qualcomm:sd_410_firmware","qualcomm:sd_412_firmware","qualcomm:sd_415_firmware","qualcomm:sd_430_firmware","qualcomm:sd_450_firmware","qualcomm:sd_615_firmware","qualcomm:sd_616_firmware","qualcomm:sd_617_firmware","qualcomm:sd_625_firmware","qualcomm:sd_650_firmware","qualcomm:sd_652_firmware","qualcomm:sd_808_firmware","qualcomm:sd_810_firmware","qualcomm:sd_820_firmware","qualcomm:sd_835_firmware"],"type":"information_disclosure","year":"2016"},"n_packages":0,"n_references":2,"next":{"headline":"Integer overflow in Snapdragon Mobile","id":"CVE-2016-10407"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2016-10405"},"products":["Snapdragon Mobile"],"published":"2018-04-18","related":[{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wearables","id":"CVE-2019-2252","kev_date_added":null,"published":"2019-09-30"},{"cvss_score":9.8,"headline":"Code injection in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wearables","id":"CVE-2019-2256","kev_date_added":null,"published":"2019-06-14"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Mobile","id":"CVE-2016-10461","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Mobile","id":"CVE-2017-18135","kev_date_added":null,"published":"2018-04-11"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Mobile","id":"CVE-2017-18142","kev_date_added":null,"published":"2018-04-11"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Mobile","id":"CVE-2018-3589","kev_date_added":null,"published":"2018-04-11"},{"cvss_score":9.1,"headline":"Privilege escalation in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile","id":"CVE-2018-11932","kev_date_added":null,"published":"2019-02-25"}],"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 attacker can read kernel memory addresses via debug logs in Qualcomm Snapdragon firmware, bypassing kptr_restrict protections.","url":"https://insights.sbomify.com/CVE-2016-10406/"}