{"answers":{"affected":"It affects 15 products.","exploited":"There is no known exploitation of CVE-2015-9194 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-9194 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-9194 is a high-severity vulnerability in Qualcomm Sd 205 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-9194 and fix it if it is affected.\n\nWhat it is: CVE-2015-9194 is a high-severity vulnerability in Qualcomm Sd 205 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-9194 in the wild and no public exploit code.\n\nAffected product: Qualcomm Sd 205 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-9194/ (Markdown: https://insights.sbomify.com/CVE-2015-9194/index.md)","id":"CVE-2015-9194","markdown":"https://insights.sbomify.com/CVE-2015-9194/index.md","name":"CVE-2015-9194","record":{"aliases":["GHSA-j78m-f6x3-h86m"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Qualcomm Snapdragon firmware","requires_auth":"none","summary":"Attackers can access sensitive information from previous applications due to uninitialized memory in Qualcomm Snapdragon firmware during module load.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"qualcomm","cpe":[{"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_425_firmware","vendor":"qualcomm"},{"product":"sd_427_firmware","vendor":"qualcomm"},{"product":"sd_430_firmware","vendor":"qualcomm"},{"product":"sd_435_firmware","vendor":"qualcomm"},{"product":"sd_450_firmware","vendor":"qualcomm"},{"product":"sd_617_firmware","vendor":"qualcomm"},{"product":"sd_625_firmware","vendor":"qualcomm"},{"product":"sd_650_firmware","vendor":"qualcomm"},{"product":"sd_652_firmware","vendor":"qualcomm"},{"product":"sd_800_firmware","vendor":"qualcomm"},{"product":"sd_845_firmware","vendor":"qualcomm"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/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":"In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile SD 210/SD 212/SD 205, SD 400, SD 425, SD 427, SD 430, SD 435, SD 450, SD 617, SD 625, SD 650/52, SD 800, SD 845, and Snapdragon_High_Med_2016, during module load at TZ Startup, memory statically allocated by modules was not being properly set to zero first. Allowing the module to execute without reset gives it access to information from previous app thus leading to information exposure.","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-2015-9194","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"qualcomm:sd_205_firmware","products":["qualcomm:sd_205_firmware","qualcomm:sd_210_firmware","qualcomm:sd_212_firmware","qualcomm:sd_400_firmware","qualcomm:sd_425_firmware","qualcomm:sd_427_firmware","qualcomm:sd_430_firmware","qualcomm:sd_435_firmware","qualcomm:sd_450_firmware","qualcomm:sd_617_firmware","qualcomm:sd_625_firmware","qualcomm:sd_650_firmware","qualcomm:sd_652_firmware","qualcomm:sd_800_firmware","qualcomm:sd_845_firmware"],"type":"information_disclosure","year":"2015"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in Snapdragon Mobile","id":"CVE-2015-9195"},"packages":[],"prev":{"headline":"Denial of service in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear","id":"CVE-2015-9193"},"products":["Snapdragon Mobile"],"published":"2018-04-18","related":[{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Mobile","id":"CVE-2014-10056","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2015-9205","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Integer overflow in Snapdragon Mobile","id":"CVE-2016-10407","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Mobile","id":"CVE-2016-10458","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Weak cryptography in Snapdragon Automobile, Snapdragon Mobile","id":"CVE-2016-10467","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Integer overflow in Snapdragon Mobile","id":"CVE-2016-10475","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Mobile","id":"CVE-2016-10477","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":"Attackers can access sensitive information from previous applications due to uninitialized memory in Qualcomm Snapdragon firmware during module load.","url":"https://insights.sbomify.com/CVE-2015-9194/"}