[Soot-list] [Android][FlowDroid] Extending FlowDroid to track input validation along the access path

[Eric Bodden]

Hui Sumaya.

I discussed this with Stevan Arzt.

This should be possible to achieve by creating a shortcut rule for the appropriate input-validation APIs. The XML rule format is described in our StubDroid-paper. A concrete example is Collection.clear(), which can be found here:
https://github.com/secure-software-engineering/soot-infoflow-summaries/blob/develop/summariesJDK/java.util.Collections%24SynchronizedList.xml

Cheers
Eric

> On 3. Apr 2019, at 21:34, Sumaya Abdullah A Almanee <salmanee at uci.edu> wrote:
> 
> Hi all,
> 
> Im currently using flowDroid to track taint propagations between certain sources and sinks. I'm also trying to check whether these sources can be controlled by an attacker and furthermore check if there is any input validation along the path (i.e. path from source to sink). For example, if the source is <com.google.android.mms.pdu.ReadRecInd: long getDate()>  which ends up getting leaked to a specific sink X(date) I want to track whether there is any input validation (such as checking the format of the date) that is applied to the info returned from getDate() before it gets leaked. 
> 
> I was wondering if this can be achieved by extending FlowDroid? if not, are you aware of any related work that can assist me in achieving this? 
> 
> Your help and time is greatly appreciated! 
> 
> Best,
> Sumaya  
> _______________________________________________
> Soot-list mailing list
> Soot-list at CS.McGill.CA
> https://mailman.CS.McGill.CA/mailman/listinfo/soot-list