LightBlog

vendredi 6 mars 2020

Google Authenticator screenshot bug could be a potential security risk

The same bug is also present in the Microsoft Authenticator Android app.

What you need to know

  • A bug in the Google Authenticator app reportedly allows screenshots of OTPs to be easily captured.
  • Security researchers had recently suggested that the "Cerberus" Android malware can steal one-time codes generated by Google Authenticator.
  • Google has been notified of the vulnerability, although it is yet to be fixed.

Security researchers at Dutch mobile security firm ThreatFabric had claimed in a report last month that the latest version of Android banking trojan Cerberus is capable of stealing one-time passcodes (OTP) generated by the Google Authenticator and other similar apps. The folks at Nightwatch Cybersecurity have now uncovered another vulnerability that could be used by malicious apps to steal one-time passcodes from Google Authenticator.

The report published by Nightwatch Cybersecurity reveals that rogue apps on Android devices might be able to steal all generated OTP codes from the Google Authenticator app, as it allows screenshots of one-time passcodes to be captured. It notes that several rogue apps make use of Android accessibility to pull screenshots from running apps. This could be prevented by using "FLAG_SECURE," but the Google Authenticator sadly does not use the FLAG_SECURE setting.

Android apps and certain platform services can capture screens from other running apps with the help of the MediaProjection API. With the FLAG_SECURE flag, the content of an app window is treated as secure, preventing it from appearing in screenshots.

While a bug report detailing the vulnerability has been submitted to Google, it hasn't been fixed yet. The bug is still present in the latest version of the Authenticator app.

Get More Pixel 3a

Google Pixel 3a

Pixel 3a From $399 at Amazon Pixel 3a XL From $479 at Amazon



from Android Central - Android Forums, News, Reviews, Help and Android Wallpapers https://ift.tt/39EJJJH
via IFTTT

Aucun commentaire:

Enregistrer un commentaire