# CVE-2020-11131: Integer overflow in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music

> An integer overflow in WMA message processing allows attackers to trigger a buffer overflow, potentially leading to code execution or privilege escalation on affected 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:** 12 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-579h-398h-hfmr

## What is CVE-2020-11131?

CVE-2020-11131 is a high-severity vulnerability in Qualcomm Apq8009 Firmware, published on 12 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

u'Possible buffer overflow in WMA message processing due to integer overflow occurs when processing command received from user space' in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music in APQ8009, APQ8053, APQ8096AU, MDM9206, MDM9250, MDM9628, MDM9640, MDM9650, MSM8996AU, QCS405, SDA845, SDX20, SDX20M, WCD9330

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2020-11131?

It affects 14 products.


Products: Qualcomm Apq8009 Firmware, Qualcomm Apq8053 Firmware, Qualcomm Apq8096au Firmware, Qualcomm Mdm9206 Firmware, Qualcomm Mdm9250 Firmware, Qualcomm Mdm9628 Firmware, Qualcomm Mdm9640 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Msm8996au Firmware, Qualcomm Qcs405 Firmware, Qualcomm Sda845 Firmware, Qualcomm Sdx20 Firmware, Qualcomm Sdx20m Firmware, Qualcomm Wcd9330 Firmware.

## How do I fix CVE-2020-11131?

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

## Is CVE-2020-11131 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8009 Firmware

- [CVE-2021-1905](https://insights.sbomify.com/CVE-2021-1905/): Qualcomm Multiple Chipsets Use-After-Free (high 8.4, exploited in the wild)
- [CVE-2020-11261](https://insights.sbomify.com/CVE-2020-11261/): Qualcomm Multiple Chipsets Improper Input Validation (high 7.8, exploited in the wild)
- [CVE-2021-1906](https://insights.sbomify.com/CVE-2021-1906/): Qualcomm Multiple Chipsets Detection of Error Condition Without Action (medium 6.2, exploited in the wild)
- [CVE-2022-40510](https://insights.sbomify.com/CVE-2022-40510/): Buffer copy without checking size of input in Audio. (critical 9.8)
- [CVE-2022-22088](https://insights.sbomify.com/CVE-2022-22088/): Integer Overflow to Buffer Overflow in Bluetooth HOST (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11131 and fix it if it is affected.

What it is: CVE-2020-11131 is a high-severity vulnerability in Qualcomm Apq8009 Firmware, published on 12 Nov 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-2020-11131 in the wild and no public exploit code.

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

## Sources

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

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