{"answers":{"affected":"It affects 20 products.","exploited":"There is no known exploitation of CVE-2019-2317 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-2317 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-2317 is a critical vulnerability in Qualcomm Msm8905 Firmware, published on 5 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-2317 and fix it if it is affected.\n\nWhat it is: CVE-2019-2317 is a critical vulnerability in Qualcomm Msm8905 Firmware, published on 5 Mar 2020. 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-2019-2317 in the wild and no public exploit code.\n\nAffected product: Qualcomm Msm8905 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-2317/ (Markdown: https://insights.sbomify.com/CVE-2019-2317/index.md)","id":"CVE-2019-2317","markdown":"https://insights.sbomify.com/CVE-2019-2317/index.md","name":"CVE-2019-2317","record":{"aliases":["GHSA-q25j-wqmf-f5jm"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Qualcomm Snapdragon SoC","requires_auth":"none","summary":"Attackers can predict TCP Initial Sequence Numbers due to weak key generation, enabling session hijacking on Qualcomm Snapdragon devices.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"qualcomm","cpe":[{"product":"msm8905_firmware","vendor":"qualcomm"},{"product":"msm8909_firmware","vendor":"qualcomm"},{"product":"msm8917_firmware","vendor":"qualcomm"},{"product":"msm8920_firmware","vendor":"qualcomm"},{"product":"msm8937_firmware","vendor":"qualcomm"},{"product":"msm8940_firmware","vendor":"qualcomm"},{"product":"msm8953_firmware","vendor":"qualcomm"},{"product":"nicobar_firmware","vendor":"qualcomm"},{"product":"qcm2150_firmware","vendor":"qualcomm"},{"product":"qm215_firmware","vendor":"qualcomm"},{"product":"sc8180x_firmware","vendor":"qualcomm"},{"product":"sdm429_firmware","vendor":"qualcomm"},{"product":"sdm439_firmware","vendor":"qualcomm"},{"product":"sdm450_firmware","vendor":"qualcomm"},{"product":"sdm632_firmware","vendor":"qualcomm"},{"product":"sdx24_firmware","vendor":"qualcomm"},{"product":"sdx55_firmware","vendor":"qualcomm"},{"product":"sm6150_firmware","vendor":"qualcomm"},{"product":"sm7150_firmware","vendor":"qualcomm"},{"product":"sm8150_firmware","vendor":"qualcomm"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-330","name":"Use of Insufficiently Random Values"}],"description":"The secret key used to make the Initial Sequence Number in the TCP SYN packet could be brute forced and therefore can be predicted in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wearables in MSM8905, MSM8909, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, Nicobar, QCM2150, QM215, SC8180X, SDM429, SDM439, SDM450, SDM632, SDX24, SDX55, SM6150, SM7150, SM8150","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":"Weak cryptography in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wearables","id":"CVE-2019-2317","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"qualcomm:msm8905_firmware","products":["qualcomm:msm8905_firmware","qualcomm:msm8909_firmware","qualcomm:msm8917_firmware","qualcomm:msm8920_firmware","qualcomm:msm8937_firmware","qualcomm:msm8940_firmware","qualcomm:msm8953_firmware","qualcomm:nicobar_firmware","qualcomm:qcm2150_firmware","qualcomm:qm215_firmware","qualcomm:sc8180x_firmware","qualcomm:sdm429_firmware","qualcomm:sdm439_firmware","qualcomm:sdm450_firmware","qualcomm:sdm632_firmware","qualcomm:sdx24_firmware","qualcomm:sdx55_firmware","qualcomm:sm6150_firmware","qualcomm:sm7150_firmware","qualcomm:sm8150_firmware"],"type":"weak_cryptography","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wired Infrastructure and Networking","id":"CVE-2019-2318"},"packages":[],"prev":{"headline":"Use after free in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Voice \u0026 Music","id":"CVE-2019-2316"},"products":["Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wearables"],"published":"2020-03-05","related":[{"cvss_score":7.5,"headline":"Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables","id":"CVE-2019-14012","kev_date_added":null,"published":"2020-04-16"},{"cvss_score":7.5,"headline":"Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables","id":"CVE-2019-10549","kev_date_added":null,"published":"2020-03-05"}],"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":"Attackers can predict TCP Initial Sequence Numbers due to weak key generation, enabling session hijacking on Qualcomm Snapdragon devices.","url":"https://insights.sbomify.com/CVE-2019-2317/"}