(#) Application's UI is vulnerable to tapjacking attacks !!! WARNING: Application's UI is vulnerable to tapjacking attacks This is a warning. Id : `TapjackingVulnerable` Summary : Application's UI is vulnerable to tapjacking attacks Severity : Warning Category : Security Platform : Android Vendor : Google - Android 3P Vulnerability Research Contact : https://github.com/google/android-security-lints Feedback : https://github.com/google/android-security-lints/issues Min : Lint 4.1 Compiled : Lint 8.0 and 8.1 Artifact : [com.android.security.lint:lint](com_android_security_lint_lint.md.html) Since : 1.0.1 Affects : Resource files Editing : This check runs on the fly in the IDE editor See : https://goo.gle/TapjackingVulnerable Implementation : [Source Code](https://github.com/google/android-security-lints/tree/main/checks/src/main/java/com/example/lint/checks/TapjackingDetector.kt) Tests : [Source Code](https://github.com/google/android-security-lints/tree/main/checks/src/test/java/com/example/lint/checks/TapjackingDetectorTest.kt) Copyright Year : 2023 Apps with sensitive UI elements should add the `filterTouchesWithObscured` attribute to protect it from tapjacking / overlay attacks. !!! Tip This lint check has an associated quickfix available in the IDE. (##) Example Here is an example of lint warnings produced by this check: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~text res/xml/switch.xml:3:Warning: Add the android:filterTouchesWhenObscured attribute to protect this UI element from tapjacking / overlay attacks [TapjackingVulnerable] <Switch android:id='enable_setting'> ------ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Here is the source file referenced above: `res/xml/switch.xml`: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~xml linenumbers <?xml version="1.0" encoding="utf-8"?> <LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"> <Switch android:id='enable_setting'> </Switch> </LinearLayout> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ You can also visit the [source code](https://github.com/google/android-security-lints/tree/main/checks/src/test/java/com/example/lint/checks/TapjackingDetectorTest.kt) for the unit tests for this check to see additional scenarios. The above example was automatically extracted from the first unit test found for this lint check, `TapjackingDetector.testWhenNamedEnableUiElement_showsWarning`. To report a problem with this extracted sample, visit https://github.com/google/android-security-lints/issues. (##) Including !!! This is not a built-in check. To include it, add the below dependency to your project. This lint check is included in the lint documentation, but the Android team may or may not agree with its recommendations. ``` // build.gradle.kts lintChecks("com.android.security.lint:lint:1.0.3") // build.gradle lintChecks 'com.android.security.lint:lint:1.0.3' // build.gradle.kts with version catalogs: lintChecks(libs.com.android.security.lint.lint) # libs.versions.toml [versions] com-android-security-lint-lint = "1.0.3" [libraries] # For clarity and text wrapping purposes the following declaration is # shown split up across lines, but in TOML it needs to be on a single # line (see https://github.com/toml-lang/toml/issues/516) so adjust # when pasting into libs.versions.toml: com-android-security-lint-lint = { module = "com.android.security.lint:lint", version.ref = "com-android-security-lint-lint" } ``` 1.0.3 is the version this documentation was generated from; there may be newer versions available. [Additional details about com.android.security.lint:lint](com_android_security_lint_lint.md.html). (##) Suppressing You can suppress false positives using one of the following mechanisms: * Adding the suppression attribute `tools:ignore="TapjackingVulnerable"` on the problematic XML element (or one of its enclosing elements). You may also need to add the following namespace declaration on the root element in the XML file if it's not already there: `xmlns:tools="http://schemas.android.com/tools"`. ```xml <?xml version="1.0" encoding="UTF-8"?> <resources xmlns:tools="http://schemas.android.com/tools"> ... <ToggleButton tools:ignore="TapjackingVulnerable" .../> ... </resources> ``` * Using a special `lint.xml` file in the source tree which turns off the check in that folder and any sub folder. A simple file might look like this: ```xml <?xml version="1.0" encoding="UTF-8"?> <lint> <issue id="TapjackingVulnerable" severity="ignore" /> </lint> ``` Instead of `ignore` you can also change the severity here, for example from `error` to `warning`. You can find additional documentation on how to filter issues by path, regular expression and so on [here](https://googlesamples.github.io/android-custom-lint-rules/usage/lintxml.md.html). * In Gradle projects, using the DSL syntax to configure lint. For example, you can use something like ```gradle lintOptions { disable 'TapjackingVulnerable' } ``` In Android projects this should be nested inside an `android { }` block. * For manual invocations of `lint`, using the `--ignore` flag: ``` $ lint --ignore TapjackingVulnerable ...` ``` * Last, but not least, using baselines, as discussed [here](https://googlesamples.github.io/android-custom-lint-rules/usage/baselines.md.html).