dbcve.org
Apq8096au FirmwareOperating system · Qualcomm

CVE-2019-14045

CRITICAL · 9.8 CVSS v3.1 Published 2020-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 while processing clientlog and serverlog due to lack of validation of data received in logs in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Mobile in APQ8096AU, QCS605, SDM439, SM8150, SXR1130

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

Buffer overflow vulnerability in clientlog and serverlog processing functions within Qualcomm Snapdragon chipsets. The vulnerability stems from insufficient validation of data received in log files, allowing potential remote or local attackers to overflow buffers and execute arbitrary code or cause denial of service.

MitigationApply vendor firmware patches from Qualcomm and device OEMs for affected chipsets. Until patches are available, restrict network access to vulnerable log processing interfaces and monitor for anomalous log data patterns.

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
Apq8096au FirmwareOperating system
Affected:all versions
Qcs605 FirmwareOperating system
Affected:all versions
Sdm439 FirmwareOperating system
Affected:all versions
Sm8150 FirmwareOperating system
Affected:all versions
Sxr1130 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 chipset model in your device or environment
    Check system information, device specifications, or use commands like 'lspci', 'cat /proc/cpuinfo', or vendor documentation to determine the Qualcomm Snapdragon chipset (APQ8096AU, QCS605, SDM439, SM8150, or SXR1130)
    Affected if The chipset matches one of the affected models: APQ8096AU, QCS605, SDM439, SM8150, or SXR1130
  2. Check the firmware version of the affected chipset
    Access device firmware settings, modem logs, or use Qualcomm diagnostic tools (such as QPST or QXDM) to retrieve the current firmware/build version
    Affected if The installed firmware version has not been patched by the vendor and falls within the 'all versions' range of the affected models
  3. Determine if clientlog or serverlog processing is enabled
    Examine system logs, debug settings, or configuration files that control log processing features. Check for enabled logging services that handle client-side or server-side log data
    Affected if Clientlog or serverlog processing functions are active and processing external log data
  4. Check for exposed log processing interfaces
    Review network accessibility of log processing services, check firewall rules, and examine any remote logging configurations that accept log data input
    Affected if Log processing interfaces are network-accessible without proper authentication or validation controls
  5. Review system logs for anomalous log data patterns
    Examine log files and system event logs for unexpected data sizes, malformed entries, or signs of buffer overflow attempts in log processing
    Affected if Logs contain unusually large log entries, truncated data, or evidence of injection attempts in clientlog/serverlog processing

You are affected if your device uses any of the chipsets APQ8096AU, QCS605, SDM439, SM8150, or SXR1130 and the log processing features are enabled or accessible, especially if firmware patches have 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 vendor firmware patches from Qualcomm and device OEMs for affected chipsets. Until patches are available, restrict network access to vulnerable log processing interfaces and monitor for anomalous log data patterns.

Fix this in Apq8096au Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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