Google Pixel Users at Risk from Dangerous Zero-Day Exploit!

Google has warned that a security flaw impacting Pixel Firmware has been exploited in the wild as a zero-day. The high-severity vulnerability, tagged as CVE-2024-32896, has been described as an elevation of privilege issue in Pixel Firmware.

Android 15 Beta 3 release takes Android 15 to Platform Stability, which means that the developer APIs and all app-facing behaviours are now final for you to review and integrate into your apps, and apps targeting Android 15 can be made available in Google Play. Thank you for all of your continued feedback in getting us to this milestone.

The official solution makes navigation easier than before, but is it type-safe? Sadly, the new API is not compile-time type-safe. And that’s a bummer because when we talk about type-safety, we expect a compile-time type-safety. I’m going to give you eight examples of where the compile-time safety of the API can fail you. Let’s dive in.

While digging through the Play Store (version 41.4.19), we found that Google is working on a way to further protect users from malicious APKs. If the Play Store is suspicious of an APK, you’ll now be required to enter a PIN or submit biometric authentication before you’ll be able to install the APK or update an app with it.

There are so many buzzwords and best practices out there, but let's focus on something more fundamental. What matters is the amount of confusion developers feel when going through the code.