Главная
Study mode:
on
1
Intro
2
android.permission.READ_LOGS
3
Why regain READ_LOGS perm
4
Notifications in the Android Log
5
Write all the sensitive data to the log
6
Regaining Android Log Access
7
Three Different Bricks
8
dumpstate binary
9
Error in native code
10
Dumpstate Files on Samsung Android
11
data/log directory
12
dumpstate file snippet
13
Create exploit application
14
Samsung vs AOSP Notifications
15
Notification ManagerServer
16
Vulnerable Builds
17
Android Platform Usage
18
Threat Mitigation
19
Conclusion
20
Questions and Discussion
Description:
Explore a critical security vulnerability discovered in Samsung devices that allows non-privileged applications to access sensitive log data, circumventing Android's READ_LOGS permission restrictions. Learn about the attack methodology, which exploits the /system/bin/dumpstate binary and requires only the RECEIVE_BOOT_COMPLETED permission. Understand how this vulnerability affects Samsung devices from Galaxy S1 to S5 and Note 4, potentially exposing private data from various applications and system processes. Discover the implications for 12 specific Samsung builds where notification content is logged by default, enabling access to sensitive information from popular messaging apps, emails, and system notifications. Examine the technical details of the exploit, including the use of the dumpstate binary, error handling in native code, and the creation of exploit applications. Compare Samsung's notification handling with AOSP (Android Open Source Project) and explore potential threat mitigation strategies. Gain insights into the broader impact on Android platform security and participate in a Q&A session to deepen your understanding of this significant security issue. Read more

Resurrecting the Read Logs Permission on Samsung Devices

Black Hat
Add to list