dbcve.org
Kamorta FirmwareOperating system · Qualcomm

CVE-2019-14123

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
Possible buffer overflow and over read possible due to missing bounds checks for fixed limits if we consider widevine HLOS client as non-trustable 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 · high confidence

Buffer overflow and over-read vulnerability in Qualcomm Snapdragon chipsets (multiple models including SM6150, SM8250, SC7180, SDX55, etc.) related to Widevine DRM. The issue exists due to missing bounds checks for fixed limits when treating the widevine HLOS client as non-trustable, potentially allowing memory corruption and unauthorized data access.

MitigationApply vendor firmware/security patches from Qualcomm and device OEMs. Organizations should identify affected devices in their fleet and coordinate with manufacturers for firmware updates.

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 device chipset model
    Determine the Qualcomm chipset model in your device (e.g., SM6150, SM8250, SC7180, SDX55, SM7150). This information is typically available in device specifications, system information, or by checking the baseband/modem firmware version via device settings or AT commands.
    Affected if The chipset model matches one of the affected models: SM6150, SM8250, SC7180, SDX55, SM7150, or related platform variants (Kamorta, Qcs404, Rennell).
  2. Check firmware version
    Retrieve the firmware version of the affected Qualcomm component. This is usually found in the device settings under 'About Phone', 'Baseband version', or through firmware extraction tools if you have root access. For embedded/network devices, check via the administrative interface or vendor diagnostic tools.
    Affected if The firmware version corresponds to Qualcomm Kamorta, Qcs404, Rennell, Sc7180, Sdx55, Sm6150, Sm7150, or Sm8250 firmware families (all versions are listed as affected).
  3. Verify Widevine DRM is in use
    Confirm that the device or application uses Widevine DRM for content protection. This can be checked by inspecting media playback capabilities, checking for Widevine DRM licensing in device specs, or using diagnostic tools that report DRM status (such as 'widevine' or 'drm' flags in system properties).
    Affected if Widevine DRM is enabled and used for media/content protection on the device. The vulnerability exists specifically in the Widevine HLOS client component.
  4. Check for trusted execution environment status
    The vulnerability relates to treating the Widevine HLOS client as non-trustable. Check the Trusted Execution Environment (TEE) configuration and whether Widevine is operating in a trusted or untrusted context. This may require vendor-specific diagnostic tools or examining security logs.
    Affected if Widevine DRM is operating with the HLOS client in a non-trusted or unverified context, or the TEE configuration allows the vulnerability condition to exist.

Your environment is affected if devices use any of the listed Qualcomm chipset firmware (Kamorta, Qcs404, Rennell, Sc7180, Sdx55, Sm6150, Sm7150, Sm8250) and utilize Widevine DRM for content protection.

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 vendor firmware/security patches from Qualcomm and device OEMs. Organizations should identify affected devices in their fleet and coordinate with manufacturers for firmware updates.

Fix this in Kamorta Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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