{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2017-18321 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-18321 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-18321 is a medium-severity vulnerability in Qualcomm Mdm9650 Firmware, published on 3 Jan 2019. 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-18321 and fix it if it is affected.\n\nWhat it is: CVE-2017-18321 is a medium-severity vulnerability in Qualcomm Mdm9650 Firmware, published on 3 Jan 2019. 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-18321 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-2017-18321/ (Markdown: https://insights.sbomify.com/CVE-2017-18321/index.md)","id":"CVE-2017-18321","markdown":"https://insights.sbomify.com/CVE-2017-18321/index.md","name":"CVE-2017-18321","record":{"aliases":["GHSA-92w7-7jg2-c4rc"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Snapdragon Mobile","requires_auth":"low_privilege","summary":"Attackers can leak session security keys from Snapdragon mobile devices, compromising communication security.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"qualcomm","cpe":[{"product":"mdm9650_firmware","vendor":"qualcomm"},{"product":"mdm9655_firmware","vendor":"qualcomm"},{"product":"sd_835_firmware","vendor":"qualcomm"},{"product":"sda660_firmware","vendor":"qualcomm"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/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":"Security keys used by the terminal and NW for a session could be leaked in snapdragon mobile in versions MDM9650, MDM9655, SD 835, SDA660.","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-2017-18321","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"qualcomm:mdm9650_firmware","products":["qualcomm:mdm9650_firmware","qualcomm:mdm9655_firmware","qualcomm:sd_835_firmware","qualcomm:sda660_firmware"],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2017-18322"},"packages":[],"prev":{"headline":"Null dereference in Snapdragon Automobile, Snapdragon Mobile","id":"CVE-2017-18320"},"products":["Snapdragon Mobile"],"published":"2019-01-03","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-08-05","vendors":["Qualcomm, Inc."]},"summary":"Attackers can leak session security keys from Snapdragon mobile devices, compromising communication security.","url":"https://insights.sbomify.com/CVE-2017-18321/"}