CVE-2019-2339
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 · uneditedOut of bound access due to lack of check of whiltelist array size while reading the image elf segments. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking in MDM9205, QCS404, QCS605, SDA845, SDM670, SDM710, SDM845, SDM850, SDX24, SDX55, SM6150, SM7150, SM8150, 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 confidenceOut-of-bounds memory access vulnerability in Qualcomm Snapdragon firmware. The ELF image parser lacks proper bounds checking when accessing a whitelist array, allowing read operations beyond array boundaries. This occurs during the processing of ELF segment headers in affected chipsets.
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 the chipset modelCheck the device or system specifications to determine the exact Qualcomm Snapdragon chipset in use. On Linux systems, this may be found in /proc/cpuinfo, /sys/devices/soc0/soc_id, or through tools like lshw, dmidecode, or vendor-specific commands such as 'cat /proc/device-tree/model'Affected if The chipset matches any of the following: Mdm9205, Qcs404, Qcs605, Sda845, Sdm670, Sdm710, Sdm845, or Sdm850
-
Verify the processing componentIdentify whether the system or component processes ELF (Executable and Linkable Format) images. This may be a bootloader, firmware update tool, or security module that loads ELF binaries. Review system logs or documentation for ELF-related operations.Affected if The affected component that parses ELF segment headers is enabled or present on the system
-
Confirm firmware is presentCheck the installed firmware version and build information. This may be accessible via vendor-specific interfaces, /proc/version, boot logs, or firmware management tools provided by the device manufacturer.Affected if Firmware is present on any of the affected chipset models listed
A system is affected if it uses any of the listed Qualcomm Snapdragon chipsets (Mdm9205, Qcs404, Qcs605, Sda845, Sdm670, Sdm710, Sdm845, Sdm850) and processes ELF images through the vulnerable firmware component.
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 dataApply vendor-provided firmware patches to affected Snapdragon chipsets. Until patches are available, limit processing of untrusted ELF images in affected components.
- Consultation8.0 h
- Implementation16.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-2339 — 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-2339 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