# CVE-2018-11948: Integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music

> An integer overflow in usage entry tracking causes data loss and content discontinuity in various Qualcomm Snapdragon firmware components.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **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:** 25 Feb 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7qr2-x27r-3mp3

## What is CVE-2018-11948?

CVE-2018-11948 is a medium-severity vulnerability in Qualcomm Msm8996au Firmware, published on 25 Feb 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Exceeding the limit of usage entries are not tracked and the information will be lost causing the content to lose continuity in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music in versions MSM8996AU, QCS605, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 625, SD 632, SD 636, SD 675, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 8CX, SDA660, SDM439, SDM630, SDM660, Snapdragon_High_Med_2016, SXR1130.

Weakness: CWE-129 (Improper Validation of Array Index)

## Which versions are affected by CVE-2018-11948?

It affects 30 products.


Products: Qualcomm Msm8996au Firmware, Qualcomm Qcs605 Firmware, Qualcomm Sd 410 Firmware, Qualcomm Sd 412 Firmware, Qualcomm Sd 425 Firmware, Qualcomm Sd 427 Firmware, Qualcomm Sd 429 Firmware, Qualcomm Sd 430 Firmware, Qualcomm Sd 435 Firmware, Qualcomm Sd 439 Firmware, Qualcomm Sd 450 Firmware, Qualcomm Sd 625 Firmware, Qualcomm Sd 632 Firmware, Qualcomm Sd 636 Firmware, Qualcomm Sd 670 Firmware, Qualcomm Sd 675 Firmware, Qualcomm Sd 710 Firmware, Qualcomm Sd 712 Firmware, Qualcomm Sd 820 Firmware, Qualcomm Sd 820a Firmware and 10 more.

## How do I fix CVE-2018-11948?

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

## Is CVE-2018-11948 being exploited?

There is no known exploitation of CVE-2018-11948 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-2018-11948 and fix it if it is affected.

What it is: CVE-2018-11948 is a medium-severity vulnerability in Qualcomm Msm8996au Firmware, published on 25 Feb 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-2018-11948 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-2018-11948/ (Markdown: https://insights.sbomify.com/CVE-2018-11948/index.md)
```

## Sources

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

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