# CVE-2019-10506: Other in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile > A Qualcomm driver fails to validate user-space data, potentially causing undesired behavior or denial of service in 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:** 30 Sep 2019 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-xvwh-qhvg-2jjx ## What is CVE-2019-10506? CVE-2019-10506 is a high-severity vulnerability in Qualcomm Mdm9206 Firmware, published on 30 Sep 2019. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description While processing QCA_NL80211_VENDOR_SUBCMD_AVOID_FREQUENCY vendor command, driver does not validate the data obtained from the user space which could be invalid and thus leads to an undesired behaviour in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in MDM9206, MDM9607, MSM8996AU, QCA6174A, QCA6574AU, QCA9377, QCA9379, QCS605, SD 600, SD 625, SD 636, SD 665, SD 675, SD 712 / SD 710 / SD 670, SD 730, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 855, SDM630, SDM660, SDX24 Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2019-10506? It affects 26 products. Products: Qualcomm Mdm9206 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Msm8996au Firmware, Qualcomm Qca6174a Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qca9377 Firmware, Qualcomm Qca9379 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Sd 600 Firmware, Qualcomm Sd 625 Firmware, Qualcomm Sd 636 Firmware, Qualcomm Sd 665 Firmware, Qualcomm Sd 670 Firmware, Qualcomm Sd 675 Firmware, Qualcomm Sd 710 Firmware, Qualcomm Sd 712 Firmware, Qualcomm Sd 730 Firmware, Qualcomm Sd 820 Firmware, Qualcomm Sd 820a Firmware, Qualcomm Sd 835 Firmware and 6 more. ## How do I fix CVE-2019-10506? No fix has been published for CVE-2019-10506 yet. Limit exposure of the affected software until one is available. ## Is CVE-2019-10506 being exploited? There is no known exploitation of CVE-2019-10506 in the wild and no public exploit code. ## Other vulnerabilities in Qualcomm Mdm9206 Firmware - [CVE-2016-10394](https://insights.sbomify.com/CVE-2016-10394/): Improper Authentication in Core (critical 9.8) - [CVE-2019-10522](https://insights.sbomify.com/CVE-2019-10522/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8) - [CVE-2019-10528](https://insights.sbomify.com/CVE-2019-10528/): Use after free in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8) - [CVE-2019-10533](https://insights.sbomify.com/CVE-2019-10533/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8) - [CVE-2019-10534](https://insights.sbomify.com/CVE-2019-10534/): Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-10506 and fix it if it is affected. What it is: CVE-2019-10506 is a high-severity vulnerability in Qualcomm Mdm9206 Firmware, published on 30 Sep 2019. 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-10506 in the wild and no public exploit code. Affected product: Qualcomm Mdm9206 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-10506/ (Markdown: https://insights.sbomify.com/CVE-2019-10506/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-10506 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-10506 - OSV: https://osv.dev/vulnerability/CVE-2019-10506 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-10506/ Summaries are generated and may contain mistakes; the official description above is the record.