CVE-2019-14104 json
Slab-out-of-bounds access can occur if the context pointer is invalid due to lack of null check on pointer before accessing it in Snapdrago…
published 6y ago modified 4mo ago also EUVD-2019-5358
- cvss
- 7.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 11%
- public exploits
- 0
- none known
Summary
Slab-out-of-bounds access can occur if the context pointer is invalid due to lack of null check on pointer before accessing it in Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Mobile in APQ8053, SC8180X, SDX55, SM8150
Patch / fix
Is CVE-2019-14104 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
| NVD | 2.0 | 6.6 | AV:L/AC:L/Au:N/C:C/I:N/A:C |
Affected products
- Qualcomm, Inc. Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Mobile
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
-
qualcomm.com
/company/product-security/bulletins/april-2020-bulletin
patch, vendor-advisory
Sources
- CVE List CVE-2019-14104
- NVD CVE-2019-14104
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.