htop
a65f1ebc545b7602f59056134cefc31001b578c026a21f3bf1a2f6f2bbf55e19
| Analysis Signal | Status | Details |
|---|---|---|
| No eXecute | Enabled | NX (No eXecute) indicates that the binary has a non-executable stack/heap (i.e., Data Execution Prevention). This prevents code from running in data sections of the process. |
| Position Independent Executable | PIE | Position Independent Executable (PIE) indicates that the binary is compiled with position-independent code, allowing it to be loaded at any address in memory. |
| Read-Only Relocations | Full | Read-Only Relocations indicate that the binary has read-only relocations, preventing modification of certain sections at runtime. |
| Stack Canary | Enabled | Stack Canary indicates that the binary uses stack canaries to detect stack buffer overflows and prevent exploitation. |
| FORTIFY | 7 / 12 | Refers to the _FORTIFY_SOURCE feature. “Partial” means some functions (like memcpy, strcpy, etc.) are protected by FORTIFY, but not all possible ones. |
| Clang CFI | Disabled | These fields being “false” simply mean the binary was not compiled with Clang’s Control Flow Integrity (CFI) or SafeStack support. |
| Clang SafeStack | Disabled | These fields being “false” simply mean the binary was not compiled with Clang’s Control Flow Integrity (CFI) or SafeStack support. |
| Stack Clash Protection | Enabled | Stack Clash Protection indicates that the binary has protections against stack clash attacks, which exploit stack memory layout. |