{"answers":{"affected":"It affects 21 products.","exploited":"There is no known exploitation of CVE-2017-18280 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-18280 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-18280 is a high-severity vulnerability in Qualcomm Mdm9607 Firmware, published on 20 Sep 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-18280 and fix it if it is affected.\n\nWhat it is: CVE-2017-18280 is a high-severity vulnerability in Qualcomm Mdm9607 Firmware, published on 20 Sep 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-18280 in the wild and no public exploit code.\n\nAffected product: Qualcomm Mdm9607 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-18280/ (Markdown: https://insights.sbomify.com/CVE-2017-18280/index.md)","id":"CVE-2017-18280","markdown":"https://insights.sbomify.com/CVE-2017-18280/index.md","name":"CVE-2017-18280","record":{"aliases":["GHSA-985h-j93g-9259"],"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 Trusted Application can read data from an open SPI/I2C interface accessed by another Trusted Application, leading to information disclosure.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"qualcomm","cpe":[{"product":"mdm9607_firmware","vendor":"qualcomm"},{"product":"msm8909w_firmware","vendor":"qualcomm"},{"product":"msm8996au_firmware","vendor":"qualcomm"},{"product":"sd205_firmware","vendor":"qualcomm"},{"product":"sd210_firmware","vendor":"qualcomm"},{"product":"sd212_firmware","vendor":"qualcomm"},{"product":"sd425_firmware","vendor":"qualcomm"},{"product":"sd427_firmware","vendor":"qualcomm"},{"product":"sd430_firmware","vendor":"qualcomm"},{"product":"sd435_firmware","vendor":"qualcomm"},{"product":"sd450_firmware","vendor":"qualcomm"},{"product":"sd617_firmware","vendor":"qualcomm"},{"product":"sd625_firmware","vendor":"qualcomm"},{"product":"sd650_firmware","vendor":"qualcomm"},{"product":"sd652_firmware","vendor":"qualcomm"},{"product":"sd820_firmware","vendor":"qualcomm"},{"product":"sd820a_firmware","vendor":"qualcomm"},{"product":"sd835_firmware","vendor":"qualcomm"},{"product":"sdm429_firmware","vendor":"qualcomm"},{"product":"sdm439_firmware","vendor":"qualcomm"},{"product":"sdm632_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":"In Snapdragon (Automobile, Mobile, Wear) in version MDM9607, MSM8909W, MSM8996AU, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 450, SD 617, SD 625, SD 650/52, SD 820, SD 820A, SD 835, SDM429, SDM439, SDM632, Snapdragon_High_Med_2016, when a Trusted Application has opened the SPI/I2C interface to a particular device, it is possible for another Trusted Application to read the data on this open interface by calling the SPI/I2C read function.","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-18280","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"qualcomm:mdm9607_firmware","products":["qualcomm:mdm9607_firmware","qualcomm:msm8909w_firmware","qualcomm:msm8996au_firmware","qualcomm:sd205_firmware","qualcomm:sd210_firmware","qualcomm:sd450_firmware","qualcomm:sd820_firmware","qualcomm:sd835_firmware","qualcomm:sdm429_firmware","qualcomm:sdm439_firmware","qualcomm:sdm632_firmware"],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in Android for MSM, Firefox OS for MSM, QRD Android","id":"CVE-2017-18281"},"packages":[],"prev":{"headline":"Integer overflow in Small Cell SoC, Snapdragon Mobile, Snapdragon Wear","id":"CVE-2017-18279"},"products":["Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear"],"published":"2018-09-20","related":[{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Auto, Snapdragon Mobile, Snapdragon Wearables","id":"CVE-2019-10531","kev_date_added":null,"published":"2019-11-06"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Voice \u0026 Music","id":"CVE-2019-2276","kev_date_added":null,"published":"2019-07-25"},{"cvss_score":9.8,"headline":"Denial of service in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear","id":"CVE-2018-5915","kev_date_added":null,"published":"2019-01-18"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2015-9126","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Mobile","id":"CVE-2016-10479","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Null dereference in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2016-10481","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Denial of service in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2017-18074","kev_date_added":null,"published":"2018-04-11"}],"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 Trusted Application can read data from an open SPI/I2C interface accessed by another Trusted Application, leading to information disclosure.","url":"https://insights.sbomify.com/CVE-2017-18280/"}