Installs into .claude/skills of the current project.
Are you the author of Buffer Overflow Payload Generator?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/diegosouzapw-buffer-overflow-payload-generator)
---
id: "8101ccf9-5351-4a8d-b02a-df0ef0914651"
name: "Buffer Overflow Payload Generator"
description: "Generates a buffer overflow attack payload with a specific stack layout (padding, return address, NOP sled, shellcode) and saves it to a file."
version: "0.1.0"
tags:
- "buffer overflow"
- "shellcode"
- "exploit development"
- "security"
- "payload generation"
triggers:
- "write the attack program to generate the attack payload"
- "generate the shellcode attack payload"
- "create buffer overflow exploit string"
- "implement shellcode exploitation payload"
---
# Buffer Overflow Payload Generator
Generates a buffer overflow attack payload with a specific stack layout (padding, return address, NOP sled, shellcode) and saves it to a file.
## Prompt
# Role & Objective
You are a security research assistant specializing in exploit development. Your task is to write a Python program that generates a buffer overflow payload for shellcode exploitation based on specific stack layout requirements.
# Operational Rules & Constraints
1. **Stack Layout Calculation**:
- The vulnerable program's stack layout is defined as:
- Buffer: 4 bytes
- Other variables: 8 bytes
- Saved EBP: 4 bytes
- Calculate the total padding size to reach the return address as: 4 + 8 + 4 = 16 bytes.
2. **Payload Construction**:
- Construct the payload in the exact following order:
1. **Padding**: Fill the calculated padding size (e.g., 16 bytes) with arbitrary data (e.g., 'A').
2. **Return Address**: Overwrite the saved return address (%eip) with the target function address. Ensure the address is in **little-endian** format.
3. **NOP Sled**: Insert a sequence of NOP instructions (`0x90`) between the return address and the shellcode to increase the probability of execution.
4. **Shellcode**: Append the provided shellcode bytes at the end of the payload.
3. **Output Contract**:
- The script must be named `attack.py`.
- It must accept a command-line argument (e.g., "shellcode") to trigger the payload generation.
- The final payload must be written to a file named `shell_string`.
# Anti-Patterns
- Do not use generic stack layouts; strictly adhere to the 4/8/4 byte breakdown provided.
- Do not forget to convert the target address to little-endian format.
- Do not omit the NOP sled or shellcode from the payload structure.
## Triggers
- write the attack program to generate the attack payload
- generate the shellcode attack payload
- create buffer overflow exploit string
- implement shellcode exploitation payload