memory-corruption-detector

You can detect memory corruption vulnerabilities in Windows binaries by running automated scanning scripts that perform taint analysis on decompiled code to surface buffer overflows, use-after-free, double-free, and format-string bugs.

Taint analysis for finding buffer overflows tracks untrusted data flow through decompiled code to identify unsafe operations. It loads module databases and flags potential memory corruption issues based on data propagation patterns.

Yes, you can verify memory-safety bugs at the assembly level. An independent verification workflow re-reads the extracted code and assembly instructions to confirm findings reported by the initial decompiled-code scanning scripts.

You can export memory corruption findings in a structured JSON format. The analysis workflow outputs vulnerability data with scoring and metadata, making it ready for runtime integration and downstream security pipelines.

This memory corruption detector is designed for Windows binaries produced by the DeepExtractIDA runtime. It leverages decompiled-code extraction and shared helpers to analyze the specific module databases generated by that environment.

Decompiled-code scanning identifies four primary types of memory corruption issues: buffer overflows, integer issues, use-after-free, double-free, and format-string bugs using dedicated detection scripts.