Whether the result of qark is reasonable or not ?

Nobody has claimed this yet.

Hi,
Recently we used qark to test google applications and found two issues as security risks.
Risk 1:
Title: android:allowTaskReparenting=”true” found
Contents: This allows an existing activity to be reparented to a new native task i.e task having
the same affinity as the activity. This may lead to UI spoofing attack on this application.
https://www.usenix.org/system/files/conference/usenixsecurity15/sec15-paper-ren-chuangang.pdf
Risk 2:
Title: android:launchMode=”singleTask” found
Contents: This results in AMS either resuming the earlier activity or loads it in a task with same
affinity or the activity is started as a new task. This may result in Task Poisoning.
https://www.usenix.org/system/files/conference/usenixsecurity15/sec15-paper-ren-chuangang.pdf

Please help us check the above two issues.
1.Whether the result of qark is reasonable or not?
2.Are there two problems actually existing in android?
3.What are the risks of these two problems?
4.If these problems do exist, how should we fix them?

Thank you.

Start by reviewing qark's reports for android:allowTaskReparenting="true" and android:launchMode="singleTask", then compare the reported risks with the linked USENIX paper and Android behavior. Done means documenting whether each finding is valid, its practical risk, and any appropriate remediation or false-positive handling.

Written by the indexing model from the issue text.