dbcve.org
Kamorta FirmwareOperating system · Qualcomm

CVE-2019-14056

HIGH · 7.8 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 →
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
u'Possible integer overflow in API due to lack of check on large oid range count in cert extension field' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in Kamorta, MDM9150, MDM9205, MDM9607, MDM9650, Nicobar, QCS404, QCS405, QCS605, QCS610, Rennell, SA6155P, SC7180, SC8180X, SDA660, SDA845, SDM630, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, 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 · moderate confidence

Integer overflow vulnerability in the certificate extension field processing API. The lack of bounds checking on the OID (Object Identifier) range count allows a specially crafted certificate with a large OID range value to trigger an integer overflow, potentially leading to memory corruption or improper memory allocation.

MitigationApply firmware/security patches released by Qualcomm and downstream device manufacturers. Identify affected devices in the environment and prioritize patching based on exposure.

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
Mdm9150 FirmwareOperating system
Affected:all versions
Mdm9205 FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Nicobar FirmwareOperating system
Affected:all versions
Qcs404 FirmwareOperating system
Affected:all versions
Qcs405 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 device model and firmware version
    Access the device's system information or settings page, or use CLI commands such as 'uname -a', 'cat /proc/version', or manufacturer-specific commands like 'getprop ro.build.version.release' on Android-based devices. Check device management interfaces or SNMP outputs if available.
    Affected if The firmware version corresponds to any of the affected Qualcomm product families: Kamorta, Mdm9150, Mdm9205, Mdm9607, Mdm9650, Nicobar, Qcs404, or Qcs405.
  2. Confirm the chipset or SoC family
    Check the device specifications via 'lspci' or 'lsusb' on embedded systems, or look up the device model against Qualcomm's product documentation to confirm it uses one of the affected chipset families.
    Affected if The device is built on one of the affected Qualcomm firmware platforms listed in the CVE.
  3. Verify if certificate processing is enabled
    Inspect the device configuration for certificate handling capabilities. Look for TLS/SSL, certificate validation, client authentication, or PKI-related modules in the device settings, config files, or running services. Check if the device accepts or processes certificates from external sources.
    Affected if The device has certificate processing, TLS, or PKI features enabled and actively processes certificates from network traffic or stored assets.
  4. Review firmware version strings
    Extract the full firmware version string from the device bootloader, recovery console, or firmware image file. Compare against any available Qualcomm patch releases or consult the device manufacturer's security advisory.
    Affected if The device firmware predates the CVE disclosure date (November 2019) and no vendor security patch has been applied.

A device is affected if it runs any of the listed Qualcomm firmware variants (Kamorta, Mdm9150, Mdm9205, Mdm9607, Mdm9650, Nicobar, Qcs404, Qcs405) and has certificate processing capabilities enabled, since all versions of these firmware families 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

Apply firmware/security patches released by Qualcomm and downstream device manufacturers. Identify affected devices in the environment and prioritize patching based on exposure.

Fix this in Kamorta Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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