CVE-2019-14130· NVD / CVE Program· CNA qualcomm

Memory corruption can occurs in trusted application if offset size from HLOS is more than actual mapped buffer size in Snapdragon Auto, Snap

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

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

HighCVSS 7.8 · v3.1—No exploit No fix recorded

Memory safety

Published: Jul 30, 2020
Updated: Jun 16, 2026
EPSS: 0.2% · 9th percentile
CWE: CWE-119

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
qualcomm	kamorta firmware	cpe:2.3:o:qualcomm:kamorta_firmware
qualcomm	kamorta	cpe:2.3:h:qualcomm:kamorta
qualcomm	qcs404 firmware	cpe:2.3:o:qualcomm:qcs404_firmware
qualcomm	qcs404	cpe:2.3:h:qualcomm:qcs404
qualcomm	rennell firmware	cpe:2.3:o:qualcomm:rennell_firmware
qualcomm	rennell	cpe:2.3:h:qualcomm:rennell
qualcomm	sc7180 firmware	cpe:2.3:o:qualcomm:sc7180_firmware
qualcomm	sc7180	cpe:2.3:h:qualcomm:sc7180
qualcomm	sdx55 firmware	cpe:2.3:o:qualcomm:sdx55_firmware
qualcomm	sdx55	cpe:2.3:h:qualcomm:sdx55
qualcomm	sm6150 firmware	cpe:2.3:o:qualcomm:sm6150_firmware
qualcomm	sm6150	cpe:2.3:h:qualcomm:sm6150

and 6 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

qualcomm kamorta firmwareall versions
qualcomm qcs404 firmwareall versions
qualcomm rennell firmwareall versions
qualcomm sc7180 firmwareall versions
qualcomm sdx55 firmwareall versions
qualcomm sm6150 firmwareall versions
qualcomm sm7150 firmwareall versions
qualcomm sm8250 firmwareall versions
qualcomm sxr2130 firmwareall versions

Versions reported by the vendor

Affected version ranges reported by the assigning authority (qualcomm). Independent of NVD's CPE analysis and usually ahead of it.

Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking
- Kamorta, QCS404, Rennell, SC7180, SDX55, SM6150, SM7150, SM8250, SXR2130affected

Same product

qualcomm: all records

Other highest-scoring records for the same primary product.

CVE-2020-3636u'Out of bound writes happen when accessing usage_table header entry beyond the memory allocated for the header' in Snapdragon Auto, Snapdra
31Monitor
CVE-2019-14089u'Keymaster attestation key and device IDs provisioning which is a one time process is incorrectly allowed to be re-provisioned after a user
31Monitor
CVE-2019-14056u'Possible integer overflow in API due to lack of check on large oid range count in cert extension field' in Snapdragon Auto, Snapdragon Com
31Monitor
CVE-2019-14124Memory failure in content protection module due to not having pointer within the scope in Snapdragon Auto, Snapdragon Compute, Snapdragon Mo
31Monitor
CVE-2019-14123Possible buffer overflow and over read possible due to missing bounds checks for fixed limits if we consider widevine HLOS client as non-tru
31Monitor
CVE-2020-3642Use after free issue in camera applications when used randomly over multiple operations due to pointer not set to NULL after free/destroy of
31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-119 · Improper Restriction of Operations within the Bounds of a Memory Buffer

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

www.qualcomm.com/company/product-security/bulletins/july-2020-bulletin

Show all references (1 more)

www.qualcomm.com/company/product-security/bulletins/july-2020-security-bulletin

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records