7.8

CVE-2019-14024

Possible stack-use-after-scope issue in NFC usecase for card emulation in Snapdragon Auto, Snapdragon Industrial IOT, Snapdragon Mobile in MSM8917, MSM8953, Nicobar, QM215, Rennell, SDM429, SDM439, SDM450, SDM632, SDM670, SDM710, SDM845, SM6150, SM7150, SM8150, SM8250, SXR2130
Daten sind bereitgestellt durch National Vulnerability Database (NVD)
Qualcomm ≫ Msm8917 Firmware Version -
   Qualcomm ≫ Msm8917 Version -
Qualcomm ≫ Msm8953 Firmware Version -
   Qualcomm ≫ Msm8953 Version -
Qualcomm ≫ Nicobar Firmware Version -
   Qualcomm ≫ Nicobar Version -
Qualcomm ≫ Qm215 Firmware Version -
   Qualcomm ≫ Qm215 Version -
Qualcomm ≫ Rennell Firmware Version -
   Qualcomm ≫ Rennell Version -
Qualcomm ≫ Sdm429 Firmware Version -
   Qualcomm ≫ Sdm429 Version -
Qualcomm ≫ Sdm439 Firmware Version -
   Qualcomm ≫ Sdm439 Version -
Qualcomm ≫ Sdm450 Firmware Version -
   Qualcomm ≫ Sdm450 Version -
Qualcomm ≫ Sdm632 Firmware Version -
   Qualcomm ≫ Sdm632 Version -
Qualcomm ≫ Sdm670 Firmware Version -
   Qualcomm ≫ Sdm670 Version -
Qualcomm ≫ Sdm710 Firmware Version -
   Qualcomm ≫ Sdm710 Version -
Qualcomm ≫ Sdm845 Firmware Version -
   Qualcomm ≫ Sdm845 Version -
Qualcomm ≫ Sm6150 Firmware Version -
   Qualcomm ≫ Sm6150 Version -
Qualcomm ≫ Sm7150 Firmware Version -
   Qualcomm ≫ Sm7150 Version -
Qualcomm ≫ Sm8150 Firmware Version -
   Qualcomm ≫ Sm8150 Version -
Qualcomm ≫ Sm8250 Firmware Version -
   Qualcomm ≫ Sm8250 Version -
Qualcomm ≫ Sxr2130 Firmware Version -
   Qualcomm ≫ Sxr2130 Version -
Zu dieser CVE wurde keine Warnung gefunden.
EPSS Metriken
Typ Quelle Score Percentile
EPSS FIRST.org 0.2% 0.101
CVSS Metriken
Quelle Base Score Exploit Score Impact Score Vector String
NIST 7.8 1.8 5.9
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NIST 7.2 3.9 10
AV:L/AC:L/Au:N/C:C/I:C/A:C
CWE-416 Use After Free

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

https://www.qualcomm.com/company/product-security/bulletins/january-2020-bulletin
Patch
Vendor Advisory