Skip to content

Callbacks which point to heap memory should be ignored #2

@william-burgess

Description

@william-burgess

Occasionally timers are found which point to non-executable heap memory:

[+] RtlCreateTimer initial allocation memory layout:
    --> 0x00007FF80D4FF578
    --> 0x00007FFFF2C20AE0
    --> 0x0000000000000001
    --> 0x000001F86D822AB0
    --> 0x000001F86D87E210 (CALLBACK)
    --> 0x00007FFFF2C43230 (PARAM)
    --> 0x0000000000000000
    --> 0x0000000000000000
    --> 0x0000000000000000
    --> 0x0000000000000000
    --> 0x0000000000000000
    --> 0x0000000000000000
    --> 0x00007FF80D4FF558
    --> 0x90001A20E54AE9AD
    --> 0x00007FF807850128
========================================================================================================
[+] Found timer-queue timer:
[+] Virtual address of ntdll!TppTimerpCleanupGroupMemberVFuncs ptr found on the heap: 0x000001F86AD55408
[+] Timer callback: 0x1f86d87e210
[+] Timer parameter: 0x7ffff2c43230
[-] Failed to resolve callback function - SymFromAddr returned error : 126
[-] GetModuleBaseName returned error : 6
[-] Manual symbol resoluton failed
========================================================================================================

As this is a valid ptr it will still be reported, as currently the only check is via IsInvalidPtr. A check could be added to see if ptr is within heap mem.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions