{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10618 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-10618 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-10618 is a medium-severity vulnerability in Qualcomm Qca6390 Firmware, published on 12 Dec 2019. 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-2019-10618 and fix it if it is affected.\n\nWhat it is: CVE-2019-10618 is a medium-severity vulnerability in Qualcomm Qca6390 Firmware, published on 12 Dec 2019. 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-2019-10618 in the wild and no public exploit code.\n\nAffected product: Qualcomm Qca6390 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-2019-10618/ (Markdown: https://insights.sbomify.com/CVE-2019-10618/index.md)","id":"CVE-2019-10618","markdown":"https://insights.sbomify.com/CVE-2019-10618/index.md","name":"CVE-2019-10618","record":{"aliases":["GHSA-rxm3-cc74-v7p3"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Snapdragon Connectivity","requires_auth":"low_privilege","summary":"A missing address validation in the Snapdragon Connectivity driver allows attackers to trigger invalid memory access, potentially causing crashes or code execution.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"qualcomm","cpe":[{"product":"qca6390_firmware","vendor":"qualcomm"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"Driver may access an invalid address while processing IO control due to lack of check of address validation in Snapdragon Connectivity in QCA6390","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":"Null dereference in Snapdragon Connectivity","id":"CVE-2019-10618","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"qualcomm:qca6390_firmware","products":["qualcomm:qca6390_firmware"],"type":"null_dereference","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2019-10619"},"packages":[],"prev":{"headline":"Information disclosure in QCA6174 9377.WIN.1.0","id":"CVE-2019-10617"},"products":["Snapdragon Connectivity"],"published":"2019-12-12","related":[{"cvss_score":8.4,"headline":"Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Wearables","id":"CVE-2021-30336","kev_date_added":null,"published":"2022-01-03"},{"cvss_score":8.1,"headline":"Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wired Infrastructure and Networking","id":"CVE-2020-11156","kev_date_added":null,"published":"2020-11-02"},{"cvss_score":6.5,"headline":"Buffer Over-read in Bluetooth HOST","id":"CVE-2023-21667","kev_date_added":null,"published":"2023-09-05"},{"cvss_score":6.5,"headline":"Improper Input Validation in Bluetooth HOST","id":"CVE-2023-21647","kev_date_added":null,"published":"2023-08-08"},{"cvss_score":6.2,"headline":"Information disclosure in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables","id":"CVE-2021-30314","kev_date_added":null,"published":"2022-01-13"}],"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-08-04","vendors":["Qualcomm, Inc."]},"summary":"A missing address validation in the Snapdragon Connectivity driver allows attackers to trigger invalid memory access, potentially causing crashes or code execution.","url":"https://insights.sbomify.com/CVE-2019-10618/"}