> For the complete documentation index, see [llms.txt](https://davidjosearaujo.gitbook.io/notes-mcs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://davidjosearaujo.gitbook.io/notes-mcs/analysis-and-exploration-of-vulnerabilities/buffers/buffer-overflow.md).
# Buffer Overflow
## According to CAPEC-100
**Targets improper or missing bounds checking on buffer operations.**
* Typically triggered by input injected by an adversary.
An adversary is able to write past the boundaries of allocated buffer regions in memory.
Causes a program crash or potentially redirection of execution as per the adversaries' choice.
* Denial of Service;
* (Remote) Code Execution.
## Scope
CWE-119 is extremely broad as there are many types of BO.
Characteristics of a BO:
* Type of access: Read or Write.
* Type of memory: stack, heap.
* Location: before or after the buffer.
* Reason: iteration, copy, pointer arithmetic, memory clear, mapping.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://davidjosearaujo.gitbook.io/notes-mcs/analysis-and-exploration-of-vulnerabilities/buffers/buffer-overflow.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.