{"answers":{"affected":"It affects 10 products.","exploited":"There is no known exploitation of CVE-2017-18313 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-18313 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-18313 is a medium-severity vulnerability in Qualcomm Msm8909w Firmware, published on 23 Oct 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-18313 and fix it if it is affected.\n\nWhat it is: CVE-2017-18313 is a medium-severity vulnerability in Qualcomm Msm8909w Firmware, published on 23 Oct 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-18313 in the wild and no public exploit code.\n\nAffected product: Qualcomm Msm8909w 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-18313/ (Markdown: https://insights.sbomify.com/CVE-2017-18313/index.md)","id":"CVE-2017-18313","markdown":"https://insights.sbomify.com/CVE-2017-18313/index.md","name":"CVE-2017-18313","record":{"aliases":["GHSA-rhv8-c8mx-v4h4"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["privilege_escalation","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Snapdragon Mobile firmware","requires_auth":"none","summary":"Attackers can tamper with authenticated WCNSS firmware via DXE channels, enabling privilege escalation on affected Snapdragon devices.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"qualcomm","cpe":[{"product":"msm8909w_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_615_firmware","vendor":"qualcomm"},{"product":"sd_616_firmware","vendor":"qualcomm"},{"product":"sd_617_firmware","vendor":"qualcomm"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[],"description":"Under certain mode of operations, HLOS may be able get direct or indirect access through DXE channels to tamper with the authenticated WCNSS firmware stored in DDR because DXE-accessible memory is located within the authenticated image in Snapdragon Mobile and Snapdragon Wear in version MSM8909W, SD 210/SD 212/SD 205, SD 410/12, SD 615/16/SD 415, SD 617.","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":"Privilege escalation in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2017-18313","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"qualcomm:msm8909w_firmware","products":["qualcomm:msm8909w_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_615_firmware","qualcomm:sd_616_firmware","qualcomm:sd_617_firmware"],"type":"privilege_escalation","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear","id":"CVE-2017-18314"},"packages":[],"prev":{"headline":"Missing authorization in Snapdragon Automobile, Snapdragon Mobile","id":"CVE-2017-18312"},"products":["Snapdragon Mobile, Snapdragon Wear"],"published":"2018-10-23","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-2285","kev_date_added":null,"published":"2019-11-06"},{"cvss_score":9.8,"headline":"Use after free in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wearables","id":"CVE-2019-10509","kev_date_added":null,"published":"2019-09-30"},{"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-10538","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-2255","kev_date_added":null,"published":"2019-06-14"},{"cvss_score":9.8,"headline":"Denial of service in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wearables","id":"CVE-2019-2259","kev_date_added":null,"published":"2019-06-14"},{"cvss_score":9.8,"headline":"SQL injection in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2017-11088","kev_date_added":null,"published":"2018-07-06"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2018-5885","kev_date_added":null,"published":"2018-07-06"}],"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":"Attackers can tamper with authenticated WCNSS firmware via DXE channels, enabling privilege escalation on affected Snapdragon devices.","url":"https://insights.sbomify.com/CVE-2017-18313/"}