The developers said that frequent Android reboots block the possibility of exploiting vulnerabilities.
The GrapheneOS development team, which created the eponymous Android operating system focused on privacy and security, proposed introducing an automatic reboot function in Android, which will complicate the exploitation of firmware vulnerabilities.
The team recently reported vulnerabilities in Android affecting Google Pixel and Samsung Galaxy smartphones. Errors can be used to steal data and track users when the device is inactive.
A device is considered "at rest" when it is turned off or not unlocked after being turned on. In this state, the level of privacy protection is very high, and the device's functionality is limited, since encryption keys are not yet available for use by installed applications.
The first unlock after a reboot moves a lot of cryptographic keys to the cache, which allows applications to work correctly, and the device comes out of rest. The GrapheneOS team notes that locking the screen after using the device does not bring it back to rest, because some security exceptions remain.
Rebooting the device ends all temporary states, processes, or actions that can be used for hacking, and requires authentication, such as PIN, password, or biometric verification, thereby restoring all security mechanisms.
GrapheneOS developers did not disclose detailed details about the exploited firmware vulnerabilities found, but offered a general solution that will be effective in most cases: the automatic reboot function, which is already present in the GrapheneOS operating system.
The function's goal is to minimize opportunities for attackers by resetting all the device's security systems more frequently than the user would. GrapheneOS auto-boot system resets the device every 18 hours.
A GrapheneOS spokesperson explained that while GrapheneOS cannot directly fix firmware errors due to hardware limitations, the new feature offers firmware memory erasure on reboot and offers improvements to the administration API to more securely delete data from the device.
GrapheneOS also notes that the airplane mode on smartphones, which many consider to reduce the risk of attacks, in fact often still allows data exchange via Wi-Fi, Bluetooth, NFC and USB Ethernet. Depending on the attack vector, flight mode may not be an effective defense measure.
The developers also address the security of PIN codes and passwords in connection with encryption systems and device security, since such authentication methods are used as keys to encrypt device data. It is important to protect against hidden search of short PIN codes and passwords, which can unlock not only the screen, but also the protected area on the device chip.
The GrapheneOS team reported on the vulnerabilities found by Google as part of the Android Vulnerability Reward Program (VRP). We are in the process of reviewing and determining the next steps.
Frequently rebooting your Android or iOS device is already considered a good idea to fix issues like overheating, memory issues, or a ring tone. From a security point of view, such an action can protect against data recovery by an attacker or other threats to mobile devices that do not have effective resilience mechanisms.
Thus, GrapheneOS proposal to introduce an automatic reboot feature in Android is based on an understanding of the importance of the process as a means of improving device security. A reboot not only helps to resolve common technical issues, but is also a key element in the fight against potential threats to data security and user privacy.
The GrapheneOS development team, which created the eponymous Android operating system focused on privacy and security, proposed introducing an automatic reboot function in Android, which will complicate the exploitation of firmware vulnerabilities.
The team recently reported vulnerabilities in Android affecting Google Pixel and Samsung Galaxy smartphones. Errors can be used to steal data and track users when the device is inactive.
A device is considered "at rest" when it is turned off or not unlocked after being turned on. In this state, the level of privacy protection is very high, and the device's functionality is limited, since encryption keys are not yet available for use by installed applications.
The first unlock after a reboot moves a lot of cryptographic keys to the cache, which allows applications to work correctly, and the device comes out of rest. The GrapheneOS team notes that locking the screen after using the device does not bring it back to rest, because some security exceptions remain.
Rebooting the device ends all temporary states, processes, or actions that can be used for hacking, and requires authentication, such as PIN, password, or biometric verification, thereby restoring all security mechanisms.
GrapheneOS developers did not disclose detailed details about the exploited firmware vulnerabilities found, but offered a general solution that will be effective in most cases: the automatic reboot function, which is already present in the GrapheneOS operating system.
The function's goal is to minimize opportunities for attackers by resetting all the device's security systems more frequently than the user would. GrapheneOS auto-boot system resets the device every 18 hours.
A GrapheneOS spokesperson explained that while GrapheneOS cannot directly fix firmware errors due to hardware limitations, the new feature offers firmware memory erasure on reboot and offers improvements to the administration API to more securely delete data from the device.
GrapheneOS also notes that the airplane mode on smartphones, which many consider to reduce the risk of attacks, in fact often still allows data exchange via Wi-Fi, Bluetooth, NFC and USB Ethernet. Depending on the attack vector, flight mode may not be an effective defense measure.
The developers also address the security of PIN codes and passwords in connection with encryption systems and device security, since such authentication methods are used as keys to encrypt device data. It is important to protect against hidden search of short PIN codes and passwords, which can unlock not only the screen, but also the protected area on the device chip.
The GrapheneOS team reported on the vulnerabilities found by Google as part of the Android Vulnerability Reward Program (VRP). We are in the process of reviewing and determining the next steps.
Frequently rebooting your Android or iOS device is already considered a good idea to fix issues like overheating, memory issues, or a ring tone. From a security point of view, such an action can protect against data recovery by an attacker or other threats to mobile devices that do not have effective resilience mechanisms.
Thus, GrapheneOS proposal to introduce an automatic reboot feature in Android is based on an understanding of the importance of the process as a means of improving device security. A reboot not only helps to resolve common technical issues, but is also a key element in the fight against potential threats to data security and user privacy.
