2019

In libavc, there is a missing variable initialization. This could lead to remote information disclosure with no addition

In libavc, there is a missing variable initialization. This could lead to remote information disclosure with no addition

In libavc, there is a missing variable initialization. This could lead to remote information disclosure with no addition

In libhevc, there is a missing variable initialization. This could lead to remote information disclosure with no additio

In libstagefright, there is a missing variable initialization. This could lead to remote information disclosure with no

In libstagefright, there is a missing variable initialization. This could lead to remote information disclosure with no

In libhevc, there is a missing variable initialization. This could lead to remote information disclosure with no additio

In libavc, there is a missing variable initialization. This could lead to remote information disclosure with no addition

In libstagefright, there is a missing variable initialization. This could lead to remote information disclosure with no

In Bluetooth, there is a possible out of bounds read due to a missing bounds check. This could lead to local information

In NFC, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl

In libstagefright, there is a possible out of bounds read due to a missing bounds check. This could lead to remote infor

In libstagefright, there is a possible out of bounds read due to a missing bounds check. This could lead to remote infor

In Bluetooth, there is a possible out of bounds read due to a missing bounds check. This could lead to local information

In libhidcommand_jni, there is a possible out of bounds write due to a missing bounds check. This could lead to local es

In Bluetooth, there is a possible out of bounds read due to a missing bounds check. This could lead to local information

In AAC Codec, there is a possible resource exhaustion due to improper input validation. This could lead to remote denial

In skia, there is a possible out of bounds read due to a missing bounds check. This could lead to remote information dis

In WiFi, there is a possible leak of WiFi state due to a permissions bypass. This could lead to a local information disc

In libstagefright, there is a possible use-after-free due to improper locking. This could lead to local escalation of pr

In sensorservice, there is a possible out of bounds write due to a missing bounds check. This could lead to local escala

In libxaac there is a possible out of bounds read due to missing bounds check. This could lead to information disclosure

In libxaac there is a possible out of bounds read due to missing bounds check. This could lead to information disclosure

In the Bluetooth stack, there is a possible out of bounds write due to a use after free. This could lead to local escala

In KeyStore, there is a possible storage of symmetric keys in the TEE instead of the strongbox due to a missing strongbo

In libavc there is a possible out of bounds read due to uninitialized data. This could lead to remote information disclo

In NFC, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl

In Bluetooth, there is a possible out of bounds read due to a missing bounds check. This could lead to local information

In AAC Codec, there is a missing variable initialization. This could lead to remote information disclosure with no addit

In NFC, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl

In NFC, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl

In wpa_supplicant_8, there is a possible out of bounds read due to a missing bounds check. This could lead to local info

In NFC, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl

In NFC, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl

In NFC, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl

In the NFC stack, there is a possible out of bounds write due to a missing bounds check. This could lead to local escala

In Bluetooth, there is a possible out of bounds read due to a missing bounds check. This could lead to remote informatio

In NFC, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl

In NFC, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl

In LG's LAF component, there is a possible leak of information in a protected disk partition due to a missing bounds che

In LG's LAF component, there is a possible leak of information in a protected disk partition due to a missing bounds che

In the Easel driver, there is possible memory corruption due to race conditions. This could lead to local escalation of

In the Easel driver, there is possible memory corruption due to race conditions. This could lead to local escalation of

In libxaac there is a possible information disclosure due to uninitialized data. This could lead to information disclosu

In libxaac there is a possible information disclosure due to uninitialized data. This could lead to information disclosu

In libxaac there is a possible information disclosure due to uninitialized data. This could lead to information disclosu

In libxaac there is a possible information disclosure due to uninitialized data. This could lead to information disclosu

In libxaac there is a possible information disclosure due to uninitialized data. This could lead to information disclosu

In libxaac there is a possible information disclosure due to uninitialized data. This could lead to information disclosu

In libxaac there is a possible information disclosure due to uninitialized data. This could lead to information disclosu