CVE-2018-5870
CVE-2018-5870 is a high-severity vulnerability in Qualcomm Sd 835 Firmware with a CVSS 3.x base score of 7.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-119.
Key facts
- Severity: High (CVSS 3.x base score 7.8)
- CVSS v2: 7.2
- EPSS exploit prediction: 0% (16th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-119
- Affected product: Qualcomm Sd 835 Firmware
- Published:
- Last modified:
Description
While loading a service image, an untrusted pointer dereference can occur in Snapdragon Mobile in versions SD 835, SDA660, SDX24.
Frequently asked questions
- What is CVE-2018-5870?
- While loading a service image, an untrusted pointer dereference can occur in Snapdragon Mobile in versions SD 835, SDA660, SDX24.
- How severe is CVE-2018-5870?
- CVE-2018-5870 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2018-5870 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (16th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2018-5870?
- CVE-2018-5870 primarily affects Qualcomm Sd 835 Firmware. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
- How do I fix CVE-2018-5870?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2018-5870 published?
- CVE-2018-5870 was published on 2018-11-28 and last updated on 2026-06-17.
References
Affected products (3)
- cpe:2.3:o:qualcomm:sd_835_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:o:qualcomm:sda660_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:o:qualcomm:sdx24_firmware:-:*:*:*:*:*:*:*
More vulnerabilities in Qualcomm Sd 835 Firmware
- CVE-2017-17772 — Critical (CVSS 9.8): In multiple functions that process 802.11 frames, out-of-bounds reads can occur due to insufficient validation.
- CVE-2017-11076 — Critical (CVSS 9.8): On some hardware revisions where VP9 decoding is hardware-accelerated, the frame size is not programmed correctly into…
- CVE-2019-2332 — Critical (CVSS 9.8): Memory corruption while accessing the memory as payload size is not validated before access in Snapdragon Auto,…
- CVE-2019-2331 — Critical (CVSS 9.8): Possible Integer overflow because of subtracting two integers without checking if the result would overflow or not in…
- CVE-2019-2325 — Critical (CVSS 9.8): Out of boundary access due to token received from ADSP and is used without validation as an index into the array in…
- CVE-2019-2323 — Critical (CVSS 9.8): Lack of check to ensure crypto engine data passed by user is initialized can result in bus error in Snapdragon Auto,…
All CVEs affecting Qualcomm Sd 835 Firmware →
Other CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) vulnerabilities
- CVE-2026-77946 — Critical (CVSS 10.0): A vulnerability was determined in TRENDnet TEW-821DAP 2.2.01b05. Affected by this vulnerability is the function…
- CVE-2026-76008 — Critical (CVSS 10.0): A flaw has been found in Comfast CF-N1-S 2.6.0.1. This affects the function get_para_from_uri of the file…
- CVE-2026-75784 — Critical (CVSS 10.0): A vulnerability was detected in TRENDnet TEW-WLC100 1v2.07b01. Affected by this issue is the function FUN_0040da4c of…
- CVE-2026-74843 — Critical (CVSS 10.0): A vulnerability was determined in Wavlink WN531P3 and WN535M1 V250922. Affected by this vulnerability is the function…
- CVE-2026-16367 — Critical (CVSS 10.0): Sandbox escape due to invalid pointer in the Disability Access APIs component. This vulnerability was fixed in Firefox…
- CVE-2026-2778 — Critical (CVSS 10.0): Sandbox escape due to incorrect boundary conditions in the DOM: Core & HTML component. This vulnerability was fixed in…