Buffer Overflow
Also called buffer overrun.
Writing past the end of a buffer to corrupt adjacent memory.
What it is
A class of memory-safety bug where a program writes more data into a fixed-size buffer than it can hold, spilling into neighboring memory. The overflow can corrupt other variables, pointers, or control data such as a saved return address.
Why it matters
Buffer overflows are one of the oldest and most exploited bug classes, often leading to code execution. Recognizing the corruption pattern in a crash dump helps responders distinguish a benign fault from an exploitation attempt.
In practice
A network service copies an oversized request into a 64-byte stack buffer, overwriting the saved return address and redirecting execution.
What to look for
- Crashes with corrupted return addresses or heap metadata.
- Unbounded copies such as strcpy or memcpy with user length.
- CVE advisories naming overflow in exposed services.
Common mistake
Assuming modern mitigations make it harmless. Combined with a leak, overflows still lead to code execution.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Risk Scoring
Score a vulnerability with CVSS v3.1, or an incident across five dimensions, and see the reasoning behind each number.
- Map and Score
Map real procedures to ATT&CK techniques, then pick the CVSS v3.1 metrics for real vulnerabilities.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Nessus Commercial
A vulnerability scanner that checks hosts for known flaws and missing patches.
-
Qualys VMDR Commercial
A cloud platform that scans assets and ranks vulnerabilities for patching.
-
OpenVAS Open source
An open source vulnerability scanner with a large set of checks.
-
Nuclei Open source
Runs community templates that test for specific, newly published flaws.
Read next
- Stack Buffer Overflow: Overflowing a stack buffer to overwrite the saved return address.
- Heap Overflow: Overflowing a heap allocation to corrupt adjacent chunks or metadata.
- Off-by-One Error: A boundary mistake of one element that corrupts adjacent memory.