Page History

Could detect possible violations of this rule by first flagging any usage of realloc(). Also, it could flag any usage of free that is not preceded by code to clear out the preceding memory, using memset. This heuristic is imperfect because it flags all possible data leaks, not just leaks of "sensitive" data, because ROSE cannot tell which data is sensitive

SV.USAGERULES.UNINTENDED_COPY

Sensitive heap memory not cleared before release

Uncleared sensitive data in stack

Sensitive data not cleared or released by memory routine