How severe is CVE-2018-13913?

CVE-2018-13913 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-13913 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (12th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2018-13913?

CVE-2018-13913 primarily affects Qualcomm Snapdragon Auto Firmware. In total, 41 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2018-13913?

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-13913 published?

CVE-2018-13913 was published on 2019-02-25 and last updated on 2026-06-17.

CVE-2018-13913

CVE-2018-13913 is a high-severity vulnerability in Qualcomm Snapdragon Auto 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-129.

Key facts

Severity: High (CVSS 3.x base score 7.8)
CVSS v2: 4.6
EPSS exploit prediction: 0% (12th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-129
Affected product: Qualcomm Snapdragon Auto Firmware
Published: 2019-02-25
Last modified: 2026-06-17

Description

Improper validation of array index can lead to unauthorized access while processing debugFS in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in version MDM9150, MDM9206, MDM9607, MDM9640, MDM9650, MSM8909W, MSM8996AU, QCS605, SD 210/SD 212/SD 205, SD 425, SD 439 / SD 429, SD 615/16/SD 415, SD 625, SD 636, SD 650/52, SD 712 / SD 710 / SD 670, SD 820A, SD 835, SD 845 / SD 850, SD 855, SDA660, SDM439, SDM630, SDM660, SDX20, SDX24.

Frequently asked questions

What is CVE-2018-13913?: Improper validation of array index can lead to unauthorized access while processing debugFS in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in version MDM9150, MDM9206, MDM9607, MDM9640, MDM9650, MSM8909W, MSM8996AU, QCS605, SD 210/SD 212/SD 205, SD 425, SD 439 / SD 429, SD 615/16/SD 415, SD 625, SD 636, SD 650/52, SD 712 / SD 710 / SD 670, SD 820A, SD 835, SD 845 / SD 850, SD 855, SDA660, SDM439, SDM630, SDM660, SDX20, SDX24.
How severe is CVE-2018-13913?: CVE-2018-13913 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-13913 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (12th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2018-13913?: CVE-2018-13913 primarily affects Qualcomm Snapdragon Auto Firmware. In total, 41 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2018-13913?: 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-13913 published?: CVE-2018-13913 was published on 2019-02-25 and last updated on 2026-06-17.

References

https://www.codeaurora.org/security-bulletin/2019/02/04/february-2019-code-aurora-security-bulletin

Affected products (41)

cpe:2.3:o:qualcomm:snapdragon_auto_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_consumer_internet_of_things_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_industrial_internet_of_things_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_internet_of_things_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_voice_\&_music_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:mdm9150_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:mdm9206_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:mdm9607_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:mdm9640_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:mdm9650_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:msm8909w_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:msm8996au_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:qcs605_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_210_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_212_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_205_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_425_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_439_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_429_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_615_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_616_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_415_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_625_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_636_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_650_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_652_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_712_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_710_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_670_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_820a_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_835_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_845_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_850_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_855_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sda660_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sdm439_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sdm630_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sdm660_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sdx20_firmware:-:*:*:*:*:*:*:*

More vulnerabilities in Qualcomm Snapdragon Auto Firmware

CVE-2018-13914 — High (CVSS 7.8): Lack of input validation for data received from user space can lead to an out of bound array issue in Snapdragon Auto,…
CVE-2018-5839 — High (CVSS 7.1): Improperly configured memory protection allows read/write access to modem image from HLOS kernel in Snapdragon Auto,…
CVE-2018-13912 — Medium (CVSS 5.5): Arbitrary write issue can occur when user provides kernel address in compat mode in Snapdragon Auto, Snapdragon…

All CVEs affecting Qualcomm Snapdragon Auto Firmware →

Other CWE-129 (Improper Validation of Array Index) vulnerabilities

CVE-2020-27485 — Critical (CVSS 9.9): Garmin Forerunner 235 before 8.20 is affected by: Array index error. The component is: ConnectIQ TVM. The attack vector…
CVE-2020-27483 — Critical (CVSS 9.9): Garmin Forerunner 235 before 8.20 is affected by: Array index error. The component is: ConnectIQ TVM. The attack vector…
CVE-2026-21413 — Critical (CVSS 9.8): A heap-based buffer overflow vulnerability exists in the lossless_jpeg_load_raw functionality of LibRaw Commit 0b56545…
CVE-2025-27034 — Critical (CVSS 9.8): Memory corruption while selecting the PLMN from SOR failed list.
CVE-2025-3357 — Critical (CVSS 9.8): IBM Tivoli Monitoring 6.3.0.7 through 6.3.0.7 Service Pack 19 could allow a remote attacker to execute arbitrary code…
CVE-2024-45569 — Critical (CVSS 9.8): Memory corruption while parsing the ML IE due to invalid frame content.

Browse all CWE-129 (Improper Validation of Array Index) vulnerabilities →