dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2019-14077

HIGH · 7.8 CVSS v3.1 Published 2020-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Out of bound memory access while processing ese transmit command due to passing Response buffer received from user in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in APQ8009, APQ8098, IPQ6018, Kamorta, MDM9150, MDM9205, MDM9607, MDM9650, MSM8909, MSM8998, Nicobar, QCS404, QCS405, QCS605, Rennell, SA415M, SA6155P, SC7180, SC8180X, SDA660, SDA845, SDM630, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SDX24, SDX55, 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 confidence

Out-of-bounds memory access vulnerability in the 'ese transmit' command handler within Qualcomm Snapdragon chipsets. The issue stems from improper validation of a Response buffer received from userspace, allowing memory access beyond allocated boundaries. This could enable local privilege escalation or information disclosure.

MitigationApply the vendor-provided security patch from Qualcomm; device manufacturers must integrate the updated firmware into their products. Users should ensure their devices receive firmware updates from their device vendors.

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 data
Apq8009 FirmwareOperating system
Affected:all versions
Apq8098 FirmwareOperating system
Affected:all versions
Ipq6018 FirmwareOperating system
Affected:all versions
Kamorta FirmwareOperating system
Affected:all versions
Mdm9150 FirmwareOperating system
Affected:all versions
Mdm9205 FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Qualcomm chipset model in the device
    Check /proc/cpuinfo, dmesg output, or system firmware tables (e.g., dmidecode on embedded systems, or check boot logs) for the chipset identifier
    Affected if The chipset model matches any of: Apq8009, Apq8098, Ipq6018, Kamorta, Mdm9150, Mdm9205, Mdm9607, Mdm9650
  2. Verify the eSE transmit feature is enabled
    Check if the embedded Secure Element (eSE) or NFC subsystem is active and the 'ese transmit' command handler is exposed. Look for related kernel modules (e.g., ese_driver, nfc_hal), service logs, or /dev/ entries related to secure element communication
    Affected if The device has an active eSE/NFC subsystem that utilizes the 'ese transmit' command path to communicate with the secure element firmware
  3. Confirm firmware version details
    Query the device firmware version through manufacturer APIs, bootloader information, or system firmware version strings (check /sys/firmware, bootloader logs, or vendor-specific AT commands for modems)
    Affected if Firmware version cannot be determined or is confirmed to be from the affected product line without vendor patch history
  4. Check for recent security patches from the device vendor
    Review device vendor release notes, security bulletins, or OTA update history for mention of Qualcomm security patches around 2019-2020
    Affected if No security patches addressing this CVE have been applied, or the patch status is unknown

The device is affected if it uses any of the listed Qualcomm chipset models (Apq8009, Apq8098, Ipq6018, Kamorta, Mdm9150, Mdm9205, Mdm9607, Mdm9650) and has the eSE transmit functionality enabled, and the vendor security patch has not been applied.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-provided security patch from Qualcomm; device manufacturers must integrate the updated firmware into their products. Users should ensure their devices receive firmware updates from their device vendors.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-14077 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-14077 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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