{"answers":{"affected":"It affects 5 products.","exploited":"There is no known exploitation of CVE-2018-3589 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-3589 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-3589 is a critical memory corruption vulnerability in Qualcomm Mdm9650 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-2018-3589 and fix it if it is affected.\n\nWhat it is: CVE-2018-3589 is a critical memory corruption vulnerability in Qualcomm Mdm9650 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-2018-3589 in the wild and no public exploit code.\n\nAffected product: Qualcomm Mdm9650 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-2018-3589/ (Markdown: https://insights.sbomify.com/CVE-2018-3589/index.md)","id":"CVE-2018-3589","markdown":"https://insights.sbomify.com/CVE-2018-3589/index.md","name":"CVE-2018-3589","record":{"aliases":["GHSA-6r5w-r8mj-phm7"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Qualcomm Snapdragon Mobile","requires_auth":"none","summary":"A buffer overflow in Qualcomm Snapdragon Mobile allows attackers to execute arbitrary code or escalate privileges via malformed diag log packets.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"qualcomm","cpe":[{"product":"mdm9650_firmware","vendor":"qualcomm"},{"product":"mdm9655_firmware","vendor":"qualcomm"},{"product":"sd_835_firmware","vendor":"qualcomm"},{"product":"sd_845_firmware","vendor":"qualcomm"},{"product":"sd_850_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-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"In Android before security patch level 2018-04-05 on Qualcomm Snapdragon Mobile MDM9650, MDM9655, SD 835, SD 845, SD 850, the vswr capture size is larger than the maximum size of a diag logPacket, which can lead to a buffer overflow when the sample buffer is copied to the logPacket buffer.","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","id":"CVE-2018-3589","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"qualcomm:mdm9650_firmware","products":["qualcomm:mdm9650_firmware","qualcomm:mdm9655_firmware","qualcomm:sd_835_firmware","qualcomm:sd_845_firmware","qualcomm:sd_850_firmware"],"type":"memory_corruption","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Use after free in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2018-3590"},"packages":[],"prev":{"headline":"Code injection in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear","id":"CVE-2018-3588"},"products":["Snapdragon Mobile"],"published":"2018-04-11","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-2252","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-2256","kev_date_added":null,"published":"2019-06-14"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Mobile","id":"CVE-2016-10461","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Mobile","id":"CVE-2017-18135","kev_date_added":null,"published":"2018-04-11"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Mobile","id":"CVE-2017-18142","kev_date_added":null,"published":"2018-04-11"},{"cvss_score":9.1,"headline":"Privilege escalation in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile","id":"CVE-2018-11932","kev_date_added":null,"published":"2019-02-25"}],"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":"A buffer overflow in Qualcomm Snapdragon Mobile allows attackers to execute arbitrary code or escalate privileges via malformed diag log packets.","url":"https://insights.sbomify.com/CVE-2018-3589/"}