# CVE-2019-2278: User keystore signature is ignored in boot and can lead to bypass boot image signature verification in Snapdragon Auto, Snapdragon Consumer


- **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
- **Fix available:** No
- **Published:** 25 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mhq7-486h-2f4f

## What is CVE-2019-2278?

CVE-2019-2278 is a high-severity vulnerability in Qualcomm Mdm9607 Firmware, published on 25 Jul 2019. 

### Official description

User keystore signature is ignored in boot and can lead to bypass boot image signature verification in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Mobile in MDM9607, MDM9640, SD 425, SD 427, SD 430, SD 435, SD 450, SD 625, SD 636, SD 712 / SD 710 / SD 670, SD 845 / SD 850, SDM660

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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

It affects 15 products.


Products: Qualcomm Mdm9607 Firmware, Qualcomm Mdm9640 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 670 Firmware, Qualcomm Sd 710 Firmware, Qualcomm Sd 712 Firmware, Qualcomm Sd 845 Firmware, Qualcomm Sd 850 Firmware, Qualcomm Sdm660 Firmware.

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

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

## Is CVE-2019-2278 being exploited?

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

## Other vulnerabilities in Qualcomm Mdm9607 Firmware

- [CVE-2019-10531](https://insights.sbomify.com/CVE-2019-10531/): Memory corruption in Snapdragon Auto, Snapdragon Mobile, Snapdragon Wearables (critical 9.8)
- [CVE-2019-2276](https://insights.sbomify.com/CVE-2019-2276/): Memory corruption in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Voice & Music (critical 9.8)
- [CVE-2018-5915](https://insights.sbomify.com/CVE-2018-5915/): Denial of service in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear (critical 9.8)
- [CVE-2015-9126](https://insights.sbomify.com/CVE-2015-9126/): Memory corruption in Snapdragon Mobile, Snapdragon Wear (critical 9.8)
- [CVE-2016-10479](https://insights.sbomify.com/CVE-2016-10479/): Memory corruption in Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-2278 is a high-severity vulnerability in Qualcomm Mdm9607 Firmware, published on 25 Jul 2019. 
Exploitation: There is no known exploitation of CVE-2019-2278 in the wild and no public exploit code.

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

## Sources

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

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