offensive-fuzzing-course

Name: offensive-fuzzing-course
Author: SnailSploit

2.8kstars447forks

How to install offensive-fuzzing-course?

snailsploit/claude-red/offensive-fuzzing-course

$npx -y skills add SnailSploit/Claude-Red --skill offensive-fuzzing-course

Installs into the current project.

Summary

When this skill is active: 1. Load and apply the full methodology below as your operational checklist 2. Follow steps in order unless the user specifies otherwise 3. For each technique, consider applicability to the current target/context 4. Track which checklist items have been

Files · 1

View on GitHub

SKILL.md

1	# SKILL: Week 2: Finding Vulnerabilities Through Fuzzing
2
3	## Metadata
4	- Skill Name: fuzzing-course
5	- Folder: offensive-fuzzing-course
6	- Source: https://github.com/SnailSploit/offensive-checklist/blob/main/2-fuzzing.md
7
8	## Description
9	Week 2 of the exploit development curriculum. Covers fuzzing methodology: target selection, corpus generation, coverage-guided fuzzing with AFL++/libFuzzer, structured fuzzing, and triage/deduplication. Use when setting up fuzz campaigns, selecting harness strategies, or triaging fuzzer output.
10
11	## Trigger Phrases
12	Use this skill when the conversation involves any of:
13	`fuzzing curriculum, AFL++, libFuzzer, coverage-guided fuzzing, corpus generation, harness, fuzz target, mutation, triage, crash dedup, week 2, exploit dev course`
14
15	## Instructions for Claude
16
17	When this skill is active:
18	1. Load and apply the full methodology below as your operational checklist
19	2. Follow steps in order unless the user specifies otherwise
20	3. For each technique, consider applicability to the current target/context
21	4. Track which checklist items have been completed
22	5. Suggest next steps based on findings
23
24	---
25
26	## Full Methodology
27
28	# Week 2: Finding Vulnerabilities Through Fuzzing
29
30	## Overview
31
32	_created by AnotherOne from @Pwn3rzs Telegram channel_.
33
34	This document is Week 2 of a multi‑week exploit development course, focusing on discovering vulnerabilities through fuzzing techniques and analyzing the crashes to determine exploitability.
35
36	Last week we studied vulnerability classes through real-world examples. This week we'll learn to find these vulnerabilities ourselves using fuzzing - the automated technique that has discovered thousands of critical security bugs in production software.
37
38	Fuzzing can feel a bit front‑loaded: you may spend time wiring harnesses and running campaigns without immediately finding exciting new bugs, especially on hardened or well‑tested targets. That’s normal, and it's one reason the next week on patch diffing often feels more directly "practical" — many companies already run large fuzzing setups and need people who can understand and exploit the bugs those systems uncover. Still, working through this week is important: it teaches you how fuzzers actually discover real vulnerabilities, so when you later triage crashes or study patches, you'll have a solid intuition for how those bugs were found and how to reproduce them.
39
40	### Prerequisites
41
42	Before starting this week, ensure you have:
43
44	- A Linux virtual machine (Ubuntu 24.04 recommended) with at least 8GB RAM and 8 cpu cores
45	- Basic understanding of C/C++ programming
46	- Familiarity with command-line tools and debugging (GDB basics)
47	- Understanding of memory corruption vulnerabilities (from Week 1)
48
49	## Day 1: Introduction to Fuzzing
50
51	- Goal: Understand the fundamentals of fuzzing and get hands-on experience with `AFL++`.
52	- Activities:
53	- _Reading_: "Fuzzing for Software Security Testing and Quality Assurance" by `Ari Takanen`(From 1.3.2 to 1.3.8 and 2.4.1 to 2.7.5).
54	- _Online Resource_:
55	- [Fuzzing Book by `Andreas Zeller`](https://www.fuzzingbook.org/) - Read "Introduction" and "Fuzzing Basics."
56	- [`AFL++` Documentation](https://aflplus.plus/docs/) - Follow the quick start guide.
57	- [Interactive Module to Learn Fuzzing](https://github.com/alex-maleno/Fuzzing-Module.git)
58	- _Real-World Context_:
59	- [Google OSS-Fuzz: Finding 36,000+ bugs across 1,000+ projects](https://google.github.io/oss-fuzz/)
60	- [AFL Success Stories](https://lcamtuf.blogspot.com/2014/11/afl-fuzz-nobody-expects-cdata-sections.html) - Real vulnerabilities found by AFL
61	- _Exercise_:
62	- Set up a Linux virtual machine (VM) with the necessary tools installed, including compilers and debuggers
63	- Run `AFL++` on a C program
64	- If possible, use or write a small C program that contains a simple version of one of the Week 1 vulnerability classes (for example, a stack buffer overflow or integer overflow) so you can see fuzzing rediscover it.
65
66	```bash
67	# Setting up AFL++
68
69	# Install build dependencies
70	sudo apt update
71	sudo apt install -y build-essential gcc-13-plugin-dev cpio python3-dev libcapstone-dev \
72	pkg-config libglib2.0-dev libpixman-1-dev automake autoconf python3-pip \
73	ninja-build cmake git wget python3.12-venv meson
74
75	# Install LLVM (check latest version at https://apt.llvm.org/)
76	wget https://apt.llvm.org/llvm.sh
77	chmod +x llvm.sh
78	sudo ./llvm.sh 19 all
79
80	# Verify LLVM installation
81	clang-19 --version
82	llvm-config-19 --version
83
84	# Install Rust (required for some AFL++ components)
85	curl --proto '=https' --tlsv1.2 -sSf "https://sh.rustup.rs" \| sh
86	source ~/.cargo/env
87
88	# Build and install AFL++
89	mkdir -p ~/soft && cd ~/soft
90	git clone --depth 1 https://github.com/AFLplusplus/AFLplusplus.git
91	cd AFLplusplus
92	# NOTE: unicorn support might fail(you need to add the env or run ./build_unicorn_support.py and fix issues yourself)
93	make distrib
94	sudo make install
95
96	# Verify installation
97	which afl-fuzz
98	afl-fuzz --version
99
100	# Phase 1: S

People who liked this also viewed

6 picks

Type

offensive-fuzzing-course

2.8kstars447forks

View on GitHub

How to install offensive-fuzzing-course?

snailsploit/claude-red/offensive-fuzzing-course

$npx -y skills add SnailSploit/Claude-Red --skill offensive-fuzzing-course

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# SKILL: Week 2: Finding Vulnerabilities Through Fuzzing
2
3	## Metadata
4	- Skill Name: fuzzing-course
5	- Folder: offensive-fuzzing-course
6	- Source: https://github.com/SnailSploit/offensive-checklist/blob/main/2-fuzzing.md
7
8	## Description
9	Week 2 of the exploit development curriculum. Covers fuzzing methodology: target selection, corpus generation, coverage-guided fuzzing with AFL++/libFuzzer, structured fuzzing, and triage/deduplication. Use when setting up fuzz campaigns, selecting harness strategies, or triaging fuzzer output.
10
11	## Trigger Phrases
12	Use this skill when the conversation involves any of:
13	`fuzzing curriculum, AFL++, libFuzzer, coverage-guided fuzzing, corpus generation, harness, fuzz target, mutation, triage, crash dedup, week 2, exploit dev course`
14
15	## Instructions for Claude
16
17	When this skill is active:
18	1. Load and apply the full methodology below as your operational checklist
19	2. Follow steps in order unless the user specifies otherwise
20	3. For each technique, consider applicability to the current target/context
21	4. Track which checklist items have been completed
22	5. Suggest next steps based on findings
23
24	---
25
26	## Full Methodology
27
28	# Week 2: Finding Vulnerabilities Through Fuzzing
29
30	## Overview
31
32	_created by AnotherOne from @Pwn3rzs Telegram channel_.
33
34	This document is Week 2 of a multi‑week exploit development course, focusing on discovering vulnerabilities through fuzzing techniques and analyzing the crashes to determine exploitability.
35
36	Last week we studied vulnerability classes through real-world examples. This week we'll learn to find these vulnerabilities ourselves using fuzzing - the automated technique that has discovered thousands of critical security bugs in production software.
37
38	Fuzzing can feel a bit front‑loaded: you may spend time wiring harnesses and running campaigns without immediately finding exciting new bugs, especially on hardened or well‑tested targets. That’s normal, and it's one reason the next week on patch diffing often feels more directly "practical" — many companies already run large fuzzing setups and need people who can understand and exploit the bugs those systems uncover. Still, working through this week is important: it teaches you how fuzzers actually discover real vulnerabilities, so when you later triage crashes or study patches, you'll have a solid intuition for how those bugs were found and how to reproduce them.
39
40	### Prerequisites
41
42	Before starting this week, ensure you have:
43
44	- A Linux virtual machine (Ubuntu 24.04 recommended) with at least 8GB RAM and 8 cpu cores
45	- Basic understanding of C/C++ programming
46	- Familiarity with command-line tools and debugging (GDB basics)
47	- Understanding of memory corruption vulnerabilities (from Week 1)
48
49	## Day 1: Introduction to Fuzzing
50
51	- Goal: Understand the fundamentals of fuzzing and get hands-on experience with `AFL++`.
52	- Activities:
53	- _Reading_: "Fuzzing for Software Security Testing and Quality Assurance" by `Ari Takanen`(From 1.3.2 to 1.3.8 and 2.4.1 to 2.7.5).
54	- _Online Resource_:
55	- [Fuzzing Book by `Andreas Zeller`](https://www.fuzzingbook.org/) - Read "Introduction" and "Fuzzing Basics."
56	- [`AFL++` Documentation](https://aflplus.plus/docs/) - Follow the quick start guide.
57	- [Interactive Module to Learn Fuzzing](https://github.com/alex-maleno/Fuzzing-Module.git)
58	- _Real-World Context_:
59	- [Google OSS-Fuzz: Finding 36,000+ bugs across 1,000+ projects](https://google.github.io/oss-fuzz/)
60	- [AFL Success Stories](https://lcamtuf.blogspot.com/2014/11/afl-fuzz-nobody-expects-cdata-sections.html) - Real vulnerabilities found by AFL
61	- _Exercise_:
62	- Set up a Linux virtual machine (VM) with the necessary tools installed, including compilers and debuggers
63	- Run `AFL++` on a C program
64	- If possible, use or write a small C program that contains a simple version of one of the Week 1 vulnerability classes (for example, a stack buffer overflow or integer overflow) so you can see fuzzing rediscover it.
65
66	```bash
67	# Setting up AFL++
68
69	# Install build dependencies
70	sudo apt update
71	sudo apt install -y build-essential gcc-13-plugin-dev cpio python3-dev libcapstone-dev \
72	pkg-config libglib2.0-dev libpixman-1-dev automake autoconf python3-pip \
73	ninja-build cmake git wget python3.12-venv meson
74
75	# Install LLVM (check latest version at https://apt.llvm.org/)
76	wget https://apt.llvm.org/llvm.sh
77	chmod +x llvm.sh
78	sudo ./llvm.sh 19 all
79
80	# Verify LLVM installation
81	clang-19 --version
82	llvm-config-19 --version
83
84	# Install Rust (required for some AFL++ components)
85	curl --proto '=https' --tlsv1.2 -sSf "https://sh.rustup.rs" \| sh
86	source ~/.cargo/env
87
88	# Build and install AFL++
89	mkdir -p ~/soft && cd ~/soft
90	git clone --depth 1 https://github.com/AFLplusplus/AFLplusplus.git
91	cd AFLplusplus
92	# NOTE: unicorn support might fail(you need to add the env or run ./build_unicorn_support.py and fix issues yourself)
93	make distrib
94	sudo make install
95
96	# Verify installation
97	which afl-fuzz
98	afl-fuzz --version
99
100	# Phase 1: S

People who liked this also viewed

6 picks

Type