Skip to content
This repository has been archived by the owner on Apr 6, 2021. It is now read-only.

Security Problem: Screenshot Function #50

Open
ThomasHabets opened this issue Aug 26, 2016 · 3 comments · May be fixed by #112
Open

Security Problem: Screenshot Function #50

ThomasHabets opened this issue Aug 26, 2016 · 3 comments · May be fixed by #112
Assignees
Labels

Comments

@ThomasHabets
Copy link
Contributor

Original issue 402 created by TriplexAccount.P.N on 2014-07-08T10:27:41.000Z:

Copied from google/google-authenticator#401 because it applies to Android app (as well?).

What steps will reproduce the problem?

  1. Call Screenshot Function from the specific smartphone

What version of the product are you using? On what operating system?
Google Authentificator: 2.49

Please provide any additional information below.
In general, it is not possible to take a screenshot of any inner user interface from a banking app for security reason. The Google Authentificator can be comprimised by using a trojan with screenshot function. Please disable the ability to take a screenshot from the main interface from the Google Authentificator.

@ThomasHabets
Copy link
Contributor Author

GA should probably use "FLAG_SECURE":: https://developer.android.com/reference/android/view/WindowManager.LayoutParams.html#FLAG_SECURE

Tethik added a commit to Tethik/google-authenticator-android that referenced this issue Feb 19, 2020
Tethik added a commit to Tethik/google-authenticator-android that referenced this issue Feb 20, 2020
@Tethik Tethik linked a pull request Feb 20, 2020 that will close this issue
@bet0x
Copy link

bet0x commented Mar 7, 2020

Something reported on 2014 gets fixed 6 years later. Great job Google.

@ThomasHabets
Copy link
Contributor Author

No, FLAG SECURE does not protect you from a11y malware (and Google couldn't have protected 2FA tokens that easily)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants