CyberSecBulletin

Stack-based Buffer Overflow

CWE-121

The product writes past the end of a buffer that was allocated on the stack.

We track 2,424 vulnerabilities of this type. 100% are rated high or critical, and the average CVSS score is 8.6. 20 have been exploited in real attacks.

How this weakness is prevented

  • Operation Build and Compilation: Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
  • Architecture and Design: Use an abstraction library to abstract away risky APIs. Not a complete solution.
  • Implementation: Implement and perform bounds checking on input.
  • Implementation: Do not use dangerous functions such as gets. Use safer, equivalent functions which check for boundary errors.

Latest Stack-based Buffer Overflow vulnerabilities