CVE-2017-18694

An issue was discovered on Samsung mobile devices with software through 2016-10-25 Exynos5 chipsets. Attackers can read kernel addresses in the log because an incorrect format specifier is used. The Samsung ID is SVE-2016-7551 January 2017...

EUVD-2017-9785

Malware in sbrugna...

Out-of-bounds

In exynos5i2cirq of TBD, there is a possible out of bounds write due to a use after free. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID:...

CVE-2022-20372

In exynos5i2cirq of TBD, there is a possible out of bounds write due to a use after free. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID:...

CVE-2022-20372

In exynos5i2cirq of TBD, there is a possible out of bounds write due to a use after free. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID:...

CVE-2017-18694

An issue was discovered on Samsung mobile devices with software through 2016-10-25 Exynos5 chipsets. Attackers can read kernel addresses in the log because an incorrect format specifier is used. The Samsung ID is SVE-2016-7551 January 2017...

Format string

An issue was discovered on Samsung mobile devices with software through 2016-10-25 Exynos5 chipsets. Attackers can read kernel addresses in the log because an incorrect format specifier is used. The Samsung ID is SVE-2016-7551 January 2017...

CVE-2017-18694

An issue was discovered on Samsung mobile devices with software through 2016-10-25 Exynos5 chipsets. Attackers can read kernel addresses in the log because an incorrect format specifier is used. The Samsung ID is SVE-2016-7551 January 2017...

CVE-2017-18694

CVE-2017-18694 affects Samsung mobile devices with Exynos5 software up to 2016-10-25. Root cause: an incorrect format specifier in the logging path allows reading kernel addresses from logs, enabling information disclosure. Impact per sources: kernel addresses disclosed; no exploitation details p...