{"answers":{"affected":"It affects 20 products.","exploited":"There is no known exploitation of CVE-2017-18316 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-18316 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-18316 is a high-severity vulnerability in Qualcomm Mdm9206 Firmware, published on 28 Nov 2018. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-18316 and fix it if it is affected.\n\nWhat it is: CVE-2017-18316 is a high-severity vulnerability in Qualcomm Mdm9206 Firmware, published on 28 Nov 2018. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-18316 in the wild and no public exploit code.\n\nAffected product: Qualcomm Mdm9206 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-2017-18316/ (Markdown: https://insights.sbomify.com/CVE-2017-18316/index.md)","id":"CVE-2017-18316","markdown":"https://insights.sbomify.com/CVE-2017-18316/index.md","name":"CVE-2017-18316","record":{"aliases":["GHSA-98mm-mrrg-w5jr"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Qualcomm Snapdragon SoC","requires_auth":"low_privilege","summary":"A secure application can access QSEE kernel memory via the Ontario kernel driver, leading to information disclosure in Qualcomm Snapdragon SoCs.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"qualcomm","cpe":[{"product":"mdm9206_firmware","vendor":"qualcomm"},{"product":"mdm9607_firmware","vendor":"qualcomm"},{"product":"mdm9650_firmware","vendor":"qualcomm"},{"product":"msm8996au_firmware","vendor":"qualcomm"},{"product":"sd_205_firmware","vendor":"qualcomm"},{"product":"sd_210_firmware","vendor":"qualcomm"},{"product":"sd_212_firmware","vendor":"qualcomm"},{"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_820_firmware","vendor":"qualcomm"},{"product":"sd_820a_firmware","vendor":"qualcomm"},{"product":"sd_835_firmware","vendor":"qualcomm"},{"product":"sd_845_firmware","vendor":"qualcomm"},{"product":"sd_850_firmware","vendor":"qualcomm"},{"product":"sda660_firmware","vendor":"qualcomm"},{"product":"sda845_firmware","vendor":"qualcomm"},{"product":"sdx24_firmware","vendor":"qualcomm"},{"product":"sxr1130_firmware","vendor":"qualcomm"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"Secure application can access QSEE kernel memory through Ontario kernel driver in Snapdragon Automobile, Snapdragon Mobile and Snapdragon Wear in versions MDM9206, MDM9607, MDM9650, MSM8996AU, SD 210/SD 212/SD 205, SD 425, SD 430, SD 450, SD 625, SD 820, SD 820A, SD 835, SD 845, SD 850, SDA660, SDA845, SDX24, SXR1130.","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 Automobile, Snapdragon Mobile, Snapdragon Wear","id":"CVE-2017-18316","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"qualcomm:mdm9206_firmware","products":["qualcomm:mdm9206_firmware","qualcomm:mdm9607_firmware","qualcomm:mdm9650_firmware","qualcomm:msm8996au_firmware","qualcomm:sd_205_firmware","qualcomm:sd_210_firmware","qualcomm:sd_212_firmware","qualcomm:sd_425_firmware","qualcomm:sd_430_firmware","qualcomm:sd_450_firmware","qualcomm:sd_625_firmware","qualcomm:sd_820_firmware","qualcomm:sd_820a_firmware","qualcomm:sd_835_firmware","qualcomm:sd_845_firmware","qualcomm:sd_850_firmware","qualcomm:sda660_firmware","qualcomm:sda845_firmware","qualcomm:sdx24_firmware","qualcomm:sxr1130_firmware"],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in Snapdragon Automobile, Snapdragon Mobile","id":"CVE-2017-18317"},"packages":[],"prev":{"headline":"Memory corruption in Snapdragon Mobile","id":"CVE-2017-18315"},"products":["Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear"],"published":"2018-11-28","related":[{"cvss_score":9.8,"headline":"Improper Authentication in Core","id":"CVE-2016-10394","kev_date_added":null,"published":"2024-11-26"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wearables","id":"CVE-2019-10522","kev_date_added":null,"published":"2019-11-06"},{"cvss_score":9.8,"headline":"Use after free in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wearables","id":"CVE-2019-10528","kev_date_added":null,"published":"2019-11-06"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wearables","id":"CVE-2019-10533","kev_date_added":null,"published":"2019-11-06"},{"cvss_score":9.8,"headline":"Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wearables","id":"CVE-2019-10534","kev_date_added":null,"published":"2019-11-06"},{"cvss_score":9.8,"headline":"Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wearables","id":"CVE-2019-10541","kev_date_added":null,"published":"2019-11-06"},{"cvss_score":9.8,"headline":"Auth bypass in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Wearables","id":"CVE-2018-11271","kev_date_added":null,"published":"2019-05-24"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["Qualcomm, Inc."]},"summary":"A secure application can access QSEE kernel memory via the Ontario kernel driver, leading to information disclosure in Qualcomm Snapdragon SoCs.","url":"https://insights.sbomify.com/CVE-2017-18316/"}