# CVE-2014-10043: Information disclosure in Snapdragon Mobile, Snapdragon Wear

> A buffer over-read in Qualcomm Snapdragon firmware allows attackers to expose Trusted Execution Environment memory to the non-secure side.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Apr 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-3873-x9wv-xhwq

## What is CVE-2014-10043?

CVE-2014-10043 is a high-severity vulnerability in Qualcomm Msm8909w Firmware, published on 18 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile and Snapdragon Wear MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, and SD 800, while reading PlayReady rights string information from command buffer (which is sent from non-secure side), if length of rights string is very large, a buffer over read occurs, exposing TZ App memory to non-secure side.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2014-10043?

It affects 8 products.


Products: Qualcomm Msm8909w Firmware, Qualcomm Sd 205 Firmware, Qualcomm Sd 210 Firmware, Qualcomm Sd 212 Firmware, Qualcomm Sd 400 Firmware, Qualcomm Sd 410 Firmware, Qualcomm Sd 412 Firmware, Qualcomm Sd 800 Firmware.

## How do I fix CVE-2014-10043?

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

## Is CVE-2014-10043 being exploited?

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

## Other vulnerabilities in Qualcomm Msm8909w Firmware

- [CVE-2019-2285](https://insights.sbomify.com/CVE-2019-2285/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-10509](https://insights.sbomify.com/CVE-2019-10509/): Use after free in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-10538](https://insights.sbomify.com/CVE-2019-10538/): 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-2255](https://insights.sbomify.com/CVE-2019-2255/): Code injection in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-2259](https://insights.sbomify.com/CVE-2019-2259/): Denial of service in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, 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-2014-10043 and fix it if it is affected.

What it is: CVE-2014-10043 is a high-severity vulnerability in Qualcomm Msm8909w Firmware, published on 18 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-10043 in the wild and no public exploit code.

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

## Sources

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

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