You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Question: Tainting / Tracking variables or memory #979
I've search for the feature of tracking variables or memory, I saw the backward slice analyses which allow me to see the flow from a certain point but I it doesn't seems to be able to track down some memory or variables.
For example if I want to track down some argv variable or track buffer return from the recv function.
Is this kind of feature exist? If not what does it take to implement it?
Can you write what is the difference between ReachingDefinitionAnalysis and DDG?
DDG is based on (simulated) forced execution, while ReachingDefinitionAnalysis is a textbook version of forward data-flow analysis. ReachingDefinitionAnalysis works on a single function (and ignores all callee functions), and it is much much faster (because it does not simulate the full execution). DDG (or CFGAccurate, because DDG simply post-processes artifacts generated during CFG recovery using CFGAccurate) takes sub-functions into consideration, and supports context sensitivity.
I haven't seen a lot of documentation on ReachingDefinitionAnalysis, can you explain what it does / how to use it?
Documentation will not be ready before that branch is ready to be merged into master.
Is it possible to taint not only register but also memory address? for example if I set argv parameters and got their addresses (in the stack) I haven't able to taint that memory address. (ddg_obj.view) doesn't contain that address.
Is there a workaround to track argv parameters / some memory address?
Activity
ltfish commentedon May 9, 2018
Do you want to do so during symbolic execution or static analysis?
mor619dx commentedon May 9, 2018
I am looking more for static analysis but I would be happy to hear both options.
ltfish commentedon May 9, 2018
Take a look at the
ReachingDefinitionAnalysis.ltfish commentedon May 9, 2018
Also, DDG on the master branch should also be useful for you in many cases.
mor619dx commentedon May 10, 2018
Can you write what is the difference between ReachingDefinitionAnalysis and DDG?
I haven't seen a lot of documentation on ReachingDefinitionAnalysis, can you explain what it does / how to use it?
ltfish commentedon May 10, 2018
DDGis based on (simulated) forced execution, whileReachingDefinitionAnalysisis a textbook version of forward data-flow analysis.ReachingDefinitionAnalysisworks on a single function (and ignores all callee functions), and it is much much faster (because it does not simulate the full execution).DDG(orCFGAccurate, becauseDDGsimply post-processes artifacts generated during CFG recovery usingCFGAccurate) takes sub-functions into consideration, and supports context sensitivity.Documentation will not be ready before that branch is ready to be merged into master.
mor619dx commentedon May 13, 2018
Alright it seems to work pretty good with DDG.
Is it possible to taint not only register but also memory address? for example if I set argv parameters and got their addresses (in the stack) I haven't able to taint that memory address. (ddg_obj.view) doesn't contain that address.
Is there a workaround to track argv parameters / some memory address?
ltfish commentedon May 21, 2018
It should track memory accesses. If not, it must be a bug.