{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-14116 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-14116 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-14116 is a high-severity vulnerability in Qualcomm Ipq6018 Firmware, published on 16 Apr 2020. 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-14116 and fix it if it is affected.\n\nWhat it is: CVE-2019-14116 is a high-severity vulnerability in Qualcomm Ipq6018 Firmware, published on 16 Apr 2020. 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-14116 in the wild and no public exploit code.\n\nAffected product: Qualcomm Ipq6018 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-14116/ (Markdown: https://insights.sbomify.com/CVE-2019-14116/index.md)","id":"CVE-2019-14116","markdown":"https://insights.sbomify.com/CVE-2019-14116/index.md","name":"CVE-2019-14116","record":{"aliases":["GHSA-j9r4-wggr-vqrx"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Qualcomm Snapdragon","requires_auth":"low_privilege","summary":"Attackers can escalate privileges by exploiting disabled XPU protections during crash dump boot flows in Qualcomm Snapdragon chipsets.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"qualcomm","cpe":[{"product":"ipq6018_firmware","vendor":"qualcomm"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Privilege escalation by using an altered debug policy image can occur as the XPU protecting the debug policy regions are disabled during the crash dump boot flow in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wired Infrastructure and Networking in IPQ6018","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":"Privilege escalation in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wired Infrastructure and Networking","id":"CVE-2019-14116","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"qualcomm:ipq6018_firmware","products":["qualcomm:ipq6018_firmware"],"type":"privilege_escalation","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Use after free in Snapdragon Auto, Snapdragon Compute, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wearables","id":"CVE-2019-14117"},"packages":[],"prev":{"headline":"Information disclosure in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking","id":"CVE-2019-14115"},"products":["Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wired Infrastructure and Networking"],"published":"2020-04-16","related":[{"cvss_score":9.8,"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-3668","kev_date_added":null,"published":"2020-09-08"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Mobile, Snapdragon Voice \u0026 Music, Snapdragon Wired Infrastructure and Networking","id":"CVE-2019-14111","kev_date_added":null,"published":"2020-04-16"},{"cvss_score":7.8,"headline":"Auth bypass in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking","id":"CVE-2019-10562","kev_date_added":null,"published":"2020-09-08"},{"cvss_score":7.8,"headline":"Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking","id":"CVE-2019-10597","kev_date_added":null,"published":"2020-06-22"},{"cvss_score":7.8,"headline":"Null dereference in Snapdragon Compute, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking","id":"CVE-2020-3618","kev_date_added":null,"published":"2020-06-02"},{"cvss_score":7.5,"headline":"Denial of service in 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-3645","kev_date_added":null,"published":"2020-06-02"}],"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-05","vendors":["Qualcomm, Inc."]},"summary":"Attackers can escalate privileges by exploiting disabled XPU protections during crash dump boot flows in Qualcomm Snapdragon chipsets.","url":"https://insights.sbomify.com/CVE-2019-14116/"}