dbcve.org
Kamorta FirmwareOperating system · Qualcomm

CVE-2019-14130

HIGH · 7.8 CVSS v3.1 Published 2020-07-30
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
Memory corruption can occurs in trusted application if offset size from HLOS is more than actual mapped buffer size in Snapdragon Auto, Snapdragon Compute, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking in Kamorta, QCS404, Rennell, SC7180, SDX55, SM6150, SM7150, SM8250, 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 · moderate confidence

Memory corruption vulnerability in trusted applications running in the Trusted Execution Environment (TEE) of Qualcomm Snapdragon chipsets. The issue occurs when the offset size provided by the HLOS (High-Level Operating System) exceeds the actual mapped buffer size, leading to an out-of-bounds memory access that can corrupt memory in the trusted application.

MitigationApply the vendor-supplied firmware/security patch from Qualcomm to affected chipsets. Devices running affected Snapdragon variants (Kamorta, QCS404, Rennell, SC7180, SDX55, SM6150, SM7150, SM8250, SXR2130) require a security update from the device manufacturer containing the fix.

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
Kamorta FirmwareOperating system
Affected:all versions
Qcs404 FirmwareOperating system
Affected:all versions
Rennell FirmwareOperating system
Affected:all versions
Sc7180 FirmwareOperating system
Affected:all versions
Sdx55 FirmwareOperating system
Affected:all versions
Sm6150 FirmwareOperating system
Affected:all versions
Sm7150 FirmwareOperating system
Affected:all versions
Sm8250 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 chipset model
    Check device specifications or use commands like 'cat /proc/cpuinfo' or 'dmesg' to find the Qualcomm Snapdragon chipset model (e.g., SM6150, SC7180, SDX55)
    Affected if The chipset matches Kamorta, QCS404, Rennell, SC7180, SDX55, SM6150, SM7150, or SM8250
  2. Check TEE availability
    Verify if the device has an active TEE by checking /dev/tee* or using 'getprop' to look for tee.* properties on Android devices
    Affected if TEE is present and actively used by the device
  3. Check HLOS-to-TEE communication paths
    Inspect application logs or security audit logs for any Trusted Application (TA) interactions that involve buffer offset parameters from the HLOS (High-Level Operating System)
    Affected if Trusted applications accept buffer offset parameters from non-secure world without proper bounds validation
  4. Determine firmware version
    Query the firmware version through vendor-specific tools or check system firmware information - note that all listed firmware versions are affected
    Affected if Firmware version cannot be determined or is older than vendor patch date (all versions listed are vulnerable)
  5. Verify vendor patch status
    Contact device manufacturer or check device security patch level in system settings (Android: Settings > Security > Security patch level)
    Affected if Security patch level is earlier than the vendor release containing the CVE-2019-14131/CVE-2019-14130 fix

A user is affected if their device uses a listed Qualcomm Snapdragon chipset (Kamorta, QCS404, Rennell, SC7180, SDX55, SM6150, SM7150, SM8250) and has not received a vendor firmware/security patch addressing this TEE memory corruption vulnerability.

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-supplied firmware/security patch from Qualcomm to affected chipsets. Devices running affected Snapdragon variants (Kamorta, QCS404, Rennell, SC7180, SDX55, SM6150, SM7150, SM8250, SXR2130) require a security update from the device manufacturer containing the fix.

Fix this in Kamorta Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing16.0 h
  • Review / QA8.0 h
36.0 hours of engineering $6,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-14130 — 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-14130 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