{"answers":{"affected":"It affects 9 products.","exploited":"There is no known exploitation of CVE-2017-18125 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-18125 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-18125 is a high-severity vulnerability in Qualcomm Mdm9206 Firmware, published on 11 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-2017-18125 and fix it if it is affected.\n\nWhat it is: CVE-2017-18125 is a high-severity vulnerability in Qualcomm Mdm9206 Firmware, published on 11 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-2017-18125 in the wild and no public exploit code.\n\nAffected product: Qualcomm Mdm9206 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-18125/ (Markdown: https://insights.sbomify.com/CVE-2017-18125/index.md)","id":"CVE-2017-18125","markdown":"https://insights.sbomify.com/CVE-2017-18125/index.md","name":"CVE-2017-18125","record":{"aliases":["GHSA-qmvp-wc85-f8m2"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Qualcomm Snapdragon","requires_auth":"none","summary":"Attackers can access stale camera data from previous sessions via protected buffer reuse in Qualcomm Snapdragon devices when secure camera is active.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"qualcomm","cpe":[{"product":"mdm9206_firmware","vendor":"qualcomm"},{"product":"mdm9607_firmware","vendor":"qualcomm"},{"product":"mdm9650_firmware","vendor":"qualcomm"},{"product":"sd_205_firmware","vendor":"qualcomm"},{"product":"sd_210_firmware","vendor":"qualcomm"},{"product":"sd_212_firmware","vendor":"qualcomm"},{"product":"sd_835_firmware","vendor":"qualcomm"},{"product":"sd_845_firmware","vendor":"qualcomm"},{"product":"sd_850_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:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-384","name":"Session Fixation"}],"description":"In Android before security patch level 2018-04-05 on Qualcomm Snapdragon Mobile and Snapdragon Wear MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205, SD 835, SD 845, SD 850, when secure camera is activated it stores captured data in protected buffers. The TEE application which uses secure camera expects those buffers to contain data captured during the current camera session. It is possible though for HLOS to put aside and reuse one or more of the protected buffers with previously captured data during next camera session. Such data reuse must be prevented as the TEE applications expects to receive valid data captured during the current session only.","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, Snapdragon Wear","id":"CVE-2017-18125","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"qualcomm:mdm9206_firmware","products":["qualcomm:mdm9206_firmware","qualcomm:mdm9607_firmware","qualcomm:mdm9650_firmware","qualcomm:sd_205_firmware","qualcomm:sd_210_firmware","qualcomm:sd_212_firmware","qualcomm:sd_835_firmware","qualcomm:sd_845_firmware","qualcomm:sd_850_firmware"],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2017-18126"},"packages":[],"prev":{"headline":"Integer overflow in Small Cell SoC, Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear","id":"CVE-2017-18124"},"products":["Snapdragon Mobile, Snapdragon Wear"],"published":"2018-04-11","related":[{"cvss_score":9.8,"headline":"Improper Authentication in Core","id":"CVE-2016-10394","kev_date_added":null,"published":"2024-11-26"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wearables","id":"CVE-2019-10522","kev_date_added":null,"published":"2019-11-06"},{"cvss_score":9.8,"headline":"Use after free in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wearables","id":"CVE-2019-10528","kev_date_added":null,"published":"2019-11-06"},{"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-10533","kev_date_added":null,"published":"2019-11-06"},{"cvss_score":9.8,"headline":"Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wearables","id":"CVE-2019-10534","kev_date_added":null,"published":"2019-11-06"},{"cvss_score":9.8,"headline":"Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wearables","id":"CVE-2019-10541","kev_date_added":null,"published":"2019-11-06"},{"cvss_score":9.8,"headline":"Auth bypass in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Wearables","id":"CVE-2018-11271","kev_date_added":null,"published":"2019-05-24"}],"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 stale camera data from previous sessions via protected buffer reuse in Qualcomm Snapdragon devices when secure camera is active.","url":"https://insights.sbomify.com/CVE-2017-18125/"}