# CVE-2019-2277: Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music

> Out-of-bounds read in WLAN firmware allows attackers to cause denial of service or disclose sensitive information via malformed data.

- **Severity:** High 7.8 (`CVSS:3.0/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:** 22 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6rvx-p9fj-cv6x

## What is CVE-2019-2277?

CVE-2019-2277 is a high-severity memory corruption vulnerability in Qualcomm Msm8996au Firmware, published on 22 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Out of bound read can happen due to lack of NULL termination on user controlled data in WLAN in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music in MSM8996AU, QCS405, QCS605, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 450, SD 625, SD 636, SD 665, SD 675, SD 712 / SD 710 / SD 670, SD 730, SD 820A, SD 835, SD 845 / SD 850, SD 855, SDA660, SDM630, SDM660, SDX24

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2019-2277?

It affects 28 products.


Products: Qualcomm Msm8996au Firmware, Qualcomm Qcs405 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Sd 205 Firmware, Qualcomm Sd 210 Firmware, Qualcomm Sd 212 Firmware, Qualcomm Sd 425 Firmware, Qualcomm Sd 427 Firmware, Qualcomm Sd 430 Firmware, Qualcomm Sd 435 Firmware, Qualcomm Sd 450 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 820a Firmware and 8 more.

## How do I fix CVE-2019-2277?

No fix has been published for CVE-2019-2277 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-2277 being exploited?

There is no known exploitation of CVE-2019-2277 in the wild and no public exploit code.

## Other vulnerabilities in Qualcomm Msm8996au Firmware

- [CVE-2017-18318](https://insights.sbomify.com/CVE-2017-18318/): Security feature bypass in Snapdragon Automobile, Snapdragon Mobile (critical 9.8)
- [CVE-2024-45555](https://insights.sbomify.com/CVE-2024-45555/): Integer Overflow to Buffer Overflow in Automotive OS Platform (high 8.4)
- [CVE-2022-33282](https://insights.sbomify.com/CVE-2022-33282/): Integer overflow to buffer overflow in Automotive Multimedia (high 8.4)
- [CVE-2022-25680](https://insights.sbomify.com/CVE-2022-25680/): Memory corruption in Snapdragon Auto (high 8.4)
- [CVE-2024-53030](https://insights.sbomify.com/CVE-2024-53030/): Improper Input Validation in Automotive OS Platform (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-2277 and fix it if it is affected.

What it is: CVE-2019-2277 is a high-severity memory corruption vulnerability in Qualcomm Msm8996au Firmware, published on 22 Jul 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-2277 in the wild and no public exploit code.

Affected product: Qualcomm Msm8996au 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-2277/ (Markdown: https://insights.sbomify.com/CVE-2019-2277/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-2277
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-2277
- OSV: https://osv.dev/vulnerability/CVE-2019-2277

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-2277/
Summaries are generated and may contain mistakes; the official description above is the record.