dbcve.org
Kamorta FirmwareOperating system · Qualcomm

CVE-2019-14025

MEDIUM · 5.5 CVSS v3.1 Published 2020-09-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
u'When a new session is created, Object is returned that contains TZ addresses and it get passed to HLOS as an handle to refer to a particular session and can cause TZ to jump to a invalid address' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking in Kamorta, QCS404, QCS610, 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

When a new session is created in the TrustZone (TZ) subsystem of affected Qualcomm Snapdragon chipsets, an object containing TZ memory addresses is returned and passed to the HLOS (High-Level Operating System) as a session handle. Due to improper validation or handling, this can cause TrustZone to jump to an invalid memory address, potentially leading to memory corruption or privilege escalation.

MitigationThis is a firmware-level vulnerability requiring firmware updates from Qualcomm/OEM vendors. Users should apply vendor-provided security patches when available and limit exposure of affected devices until patches are deployed.

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
Qcs610 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

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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 device chipset model
    Use commands such as 'cat /proc/cpuinfo' or check system information to determine the Qualcomm Snapdragon chipset model (e.g., SM6150, SC7180, etc.)
    Affected if The chipset matches any of the following: Kamorta, QCS404, QCS610, Rennell, SC7180, SDX55, SM6150, or SM7150
  2. Verify the chipset is a Qualcomm Snapdragon processor
    Confirm the processor is a Qualcomm Snapdragon SoC that includes TrustZone (TZ) technology - these are ARM-based chipsets with a Trusted Execution Environment
    Affected if The processor is not a Qualcomm Snapdragon chipset with TrustZone (non-Qualcomm or older chips without TZ)
  3. Check TrustZone firmware version
    Attempt to read TZ firmware version via vendor-specific interfaces (such as 'cat /sys/firmware/efi/esrt/entries/esrt0000/version' or vendor diagnostic tools if available) or check the baseband/modem firmware version which often shares versioning with TZ
    Affected if The firmware version cannot be determined or the installed version falls within the affected ranges (which is all versions for the listed chipsets)
  4. Confirm TrustZone session handling is in use
    Verify the device uses TrustZone for security-sensitive operations (this is typically always enabled on affected Snapdragon chipsets by default)
    Affected if TrustZone is actively being used for secure sessions, which is the default state on these chipsets

If the device uses any of the affected Qualcomm Snapdragon chipsets (Kamorta, QCS404, QCS610, Rennell, SC7180, SDX55, SM6150, or SM7150) with TrustZone enabled, the environment is likely affected since all firmware versions of these chipsets are vulnerable.

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

This is a firmware-level vulnerability requiring firmware updates from Qualcomm/OEM vendors. Users should apply vendor-provided security patches when available and limit exposure of affected devices until patches are deployed.

Fix this in Kamorta Firmware Scoped from the published advisory
  • Consultation8.0 h
8.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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