{"answers":{"affected":"It affects 18 products.","exploited":"There is no known exploitation of CVE-2015-9208 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-9208 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-9208 is a critical memory corruption vulnerability in Qualcomm Ipq4019 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-2015-9208 and fix it if it is affected.\n\nWhat it is: CVE-2015-9208 is a critical memory corruption vulnerability in Qualcomm Ipq4019 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-2015-9208 in the wild and no public exploit code.\n\nAffected product: Qualcomm Ipq4019 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-2015-9208/ (Markdown: https://insights.sbomify.com/CVE-2015-9208/index.md)","id":"CVE-2015-9208","markdown":"https://insights.sbomify.com/CVE-2015-9208/index.md","name":"CVE-2015-9208","record":{"aliases":["GHSA-p87q-j7mq-759c"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Qualcomm Snapdragon firmware","requires_auth":"none","summary":"Insufficient memory boundary checks in Qualcomm Snapdragon firmware allow attackers to bypass secure memory protections, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"qualcomm","cpe":[{"product":"ipq4019_firmware","vendor":"qualcomm"},{"product":"mdm9206_firmware","vendor":"qualcomm"},{"product":"mdm9607_firmware","vendor":"qualcomm"},{"product":"mdm9635m_firmware","vendor":"qualcomm"},{"product":"mdm9640_firmware","vendor":"qualcomm"},{"product":"mdm9645_firmware","vendor":"qualcomm"},{"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_400_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_800_firmware","vendor":"qualcomm"},{"product":"sd_810_firmware","vendor":"qualcomm"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile and Snapdragon Wear IPQ4019, MDM9206, MDM9607, MDM9635M, MDM9640, MDM9645, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 615/16/SD 415, SD 800, and SD 810, the function tzbsp_pil_verify_sig() does not strictly check that the pointer to ELF and program headers and hash segment is within secure memory. It only checks that the address is not in non-secure memory. A given address range can overlap with both secure and non-secure regions - hence if such an address is passed in, it would not pass the non-secure range check, and would be considered valid by the function, even though that memory area could be modified by the non-secure side.","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":"Memory corruption in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2015-9208","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"qualcomm:ipq4019_firmware","products":["qualcomm:ipq4019_firmware","qualcomm:mdm9206_firmware","qualcomm:mdm9607_firmware","qualcomm:mdm9635m_firmware","qualcomm:mdm9640_firmware","qualcomm:mdm9645_firmware","qualcomm:msm8909w_firmware","qualcomm:sd_205_firmware","qualcomm:sd_210_firmware","qualcomm:sd_212_firmware","qualcomm:sd_400_firmware","qualcomm:sd_410_firmware","qualcomm:sd_412_firmware","qualcomm:sd_415_firmware","qualcomm:sd_615_firmware","qualcomm:sd_616_firmware","qualcomm:sd_800_firmware","qualcomm:sd_810_firmware"],"type":"memory_corruption","year":"2015"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2015-9209"},"packages":[],"prev":{"headline":"Memory corruption in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2015-9207"},"products":["Snapdragon Mobile, Snapdragon Wear"],"published":"2018-04-18","related":[{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Wired Infrastructure and Networking","id":"CVE-2020-11172","kev_date_added":null,"published":"2020-11-02"},{"cvss_score":9.8,"headline":"Command injection in Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Wired Infrastructure and Networking","id":"CVE-2020-11117","kev_date_added":null,"published":"2020-09-08"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2014-10045","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear","id":"CVE-2014-9988","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear IPQ40","id":"CVE-2014-9998","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Denial of service in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear","id":"CVE-2015-9120","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2015-9143","kev_date_added":null,"published":"2018-04-18"}],"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":"Insufficient memory boundary checks in Qualcomm Snapdragon firmware allow attackers to bypass secure memory protections, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2015-9208/"}