Skip to content

Question: Tainting / Tracking variables or memory #979

Closed

Description

@mor619dx

Hello,

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?

Activity

  1. ltfish commented on May 9, 2018

    @ltfish
    Member

    Do you want to do so during symbolic execution or static analysis?

  2. added
    questionIssues that do not require code changes
    on May 9, 2018
  3. mor619dx commented on May 9, 2018

    @mor619dx
    ContributorAuthor

    I am looking more for static analysis but I would be happy to hear both options.

  4. ltfish commented on May 9, 2018

    @ltfish
    Member

    Take a look at the ReachingDefinitionAnalysis.

  5. ltfish commented on May 9, 2018

    @ltfish
    Member

    Also, DDG on the master branch should also be useful for you in many cases.

  6. mor619dx commented on May 10, 2018

    @mor619dx
    ContributorAuthor

    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?

  7. ltfish commented on May 10, 2018

    @ltfish
    Member

    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.

  8. mor619dx commented on May 13, 2018

    @mor619dx
    ContributorAuthor

    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?

  9. ltfish commented on May 21, 2018

    @ltfish
    Member

    Is there a workaround to track argv parameters / some memory address?

    It should track memory accesses. If not, it must be a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionIssues that do not require code changes

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions