# CVE-2019-14049: Denial of service in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music > A stage-2 fault occurs when writing to specific ION memory allocations, causing a denial of service on affected Qualcomm Snapdragon devices. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 7 Feb 2020 - **Updated:** 5 Aug 2024 - **Also known as:** GHSA-pvqf-f4m8-593f ## What is CVE-2019-14049? CVE-2019-14049 is a high-severity denial of service vulnerability in Qualcomm Apq8017 Firmware, published on 7 Feb 2020. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Stage-2 fault will occur while writing to an ION system allocation which has been assigned to non-HLOS memory which is non-standard in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music in APQ8017, APQ8053, APQ8096AU, MDM9206, MDM9207C, MDM9607, MDM9640, MSM8953, QCN7605, QCS605, SC8180X, SDA845, SDM429, SDM439, SDM450, SDM632, SDX20, SDX24, SDX55, SM8150, SXR1130 Weakness: CWE-617 (Reachable Assertion) ## Which versions are affected by CVE-2019-14049? It affects 21 products. Products: Qualcomm Apq8017 Firmware, Qualcomm Apq8053 Firmware, Qualcomm Apq8096au Firmware, Qualcomm Mdm9206 Firmware, Qualcomm Mdm9207c Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9640 Firmware, Qualcomm Msm8953 Firmware, Qualcomm Qcn7605 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Sc8180x Firmware, Qualcomm Sda845 Firmware, Qualcomm Sdm429 Firmware, Qualcomm Sdm439 Firmware, Qualcomm Sdm450 Firmware, Qualcomm Sdm632 Firmware, Qualcomm Sdx20 Firmware, Qualcomm Sdx24 Firmware, Qualcomm Sdx55 Firmware, Qualcomm Sm8150 Firmware and 1 more. ## How do I fix CVE-2019-14049? No fix has been published for CVE-2019-14049 yet. Limit exposure of the affected software until one is available. ## Is CVE-2019-14049 being exploited? There is no known exploitation of CVE-2019-14049 in the wild and no public exploit code. ## Other vulnerabilities in Qualcomm Apq8017 Firmware - [CVE-2025-21483](https://insights.sbomify.com/CVE-2025-21483/): Improper Restriction of Operations within the Bounds of a Memory Buffer in Data Network Stack & Connectivity (critical 9.8) - [CVE-2021-1933](https://insights.sbomify.com/CVE-2021-1933/): Denial of service in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Wearables (critical 9.8) - [CVE-2021-1946](https://insights.sbomify.com/CVE-2021-1946/): Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile (critical 9.8) - [CVE-2020-11176](https://insights.sbomify.com/CVE-2020-11176/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile (critical 9.8) - [CVE-2020-11291](https://insights.sbomify.com/CVE-2020-11291/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-14049 and fix it if it is affected. What it is: CVE-2019-14049 is a high-severity denial of service vulnerability in Qualcomm Apq8017 Firmware, published on 7 Feb 2020. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2019-14049 in the wild and no public exploit code. Affected product: Qualcomm Apq8017 Firmware. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2019-14049/ (Markdown: https://insights.sbomify.com/CVE-2019-14049/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-14049 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-14049 - OSV: https://osv.dev/vulnerability/CVE-2019-14049 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-14049/ Summaries are generated and may contain mistakes; the official description above is the record.