Research Article
Tag-Protector: An Effective and Dynamic Detection of Illegal Memory Accesses through Compile Time Code Instrumentation
Table 2
Comprehensive comparison with existing publicly available countermeasures when tested on Ubuntu 12.4 64-bit architecture.
| Technique used | Buffer overow location | Dangling pointer detection | Detection rate for RIPE [47] | Stack | Heap | Data segment | Bss segment | Structs2 |
| gcc compiled no protection | | | | | | | 0% | LibSafe [36] | | | | | | | 7% | StackShield [38] | | | | | | | 36% | ProPolice [37] | | | | | | | 40% | LibsafePlus + TIED [39, 40] | | | | | | | 70% | CRED [9] | | | | | | | 60% | SoftBound [20] | | | | | | | 36.26% | SAFECode [10] | | | | | | | 68.89% | AddressSanitizer [35] | | | | | | | 85.5% | Proposed Tag-Protector | | | | | | | 100% |
|
|