CVE-2019-2251
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIf a bitmap file is loaded from any un-authenticated source, there is a possibility that the bitmap can potentially cause stack buffer overflow. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music in APQ8016, APQ8096AU, APQ8098, MDM9205, MSM8996AU, MSM8998, Nicobar, QCS405, QCS605, SA6155P, SC8180X, SDA660, SDA845, SDM630, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SDX24, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceStack buffer overflow vulnerability in bitmap file parsing within multiple Qualcomm Snapdragon chipset families. When loading bitmap files from un-authenticated sources, the parsing logic fails to properly validate bounds, allowing data to overflow stack-allocated buffers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify chipset modelDetermine the exact Qualcomm Snapdragon chipset model present in your device or system. This information is typically found in system information, device specifications, or through firmware/system queries (e.g., 'lspci' for PCI devices, 'cat /proc/cpuinfo' on embedded Linux systems, or check boot logs).Affected if The chipset matches one of: Apq8016, Apq8096au, Apq8098, Mdm9205, Msm8996au, Msm8998, Nicobar, or Qcs405.
-
Confirm firmware is Qualcomm-basedVerify that the firmware running on the device is Qualcomm firmware and not an alternative implementation. Check boot logs, firmware headers, or system diagnostics that indicate the firmware vendor.Affected if The firmware is confirmed to be from the affected Qualcomm product line.
-
Assess bitmap file loading exposureEvaluate whether the system or application can load bitmap files from untrusted or unauthenticated sources. This includes checking if there are features that accept bitmap uploads, process image files from external inputs, or parse bitmap files as part of normal operation.Affected if Bitmap files from untrusted sources can be loaded or processed by the system.
-
Check for vulnerable bitmap parsing featureIdentify if the firmware includes bitmap parsing functionality. This is typically present in graphics processing, image viewing, or multimedia components. Check enabled features/modules related to image handling.Affected if Bitmap parsing feature is enabled and operational on the device.
If your device uses one of the affected Qualcomm chipset models (Apq8016, Apq8096au, Apq8098, Mdm9205, Msm8996au, Msm8998, Nicobar, or Qcs405) and can load bitmap files from untrusted sources, then your environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataAvoid loading bitmap files from untrusted/unauthenticated sources; apply vendor firmware patches when released; implement input validation and bounds checking on bitmap parsing code.
- Consultation8.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-2251 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-2251 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data