offensive-vuln-classes

Name: offensive-vuln-classes
Author: SnailSploit

2.8kstars447forks

How to install offensive-vuln-classes?

snailsploit/claude-red/offensive-vuln-classes

$npx -y skills add SnailSploit/Claude-Red --skill offensive-vuln-classes

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 1: Vulnerability Classes with Real-World Examples
2
3	## Metadata
4	- Skill Name: vulnerability-classes
5	- Folder: offensive-vuln-classes
6	- Source: https://github.com/SnailSploit/offensive-checklist/blob/main/1-vulnerability-classes.md
7
8	## Description
9	Exploit development curriculum covering core vulnerability classes with real-world CVE case studies: stack/heap buffer overflows, use-after-free, integer overflows, format strings, type confusion, and race conditions. Use when learning or teaching vuln classes, researching specific CVE patterns, or building exploit dev knowledge.
10
11	## Trigger Phrases
12	Use this skill when the conversation involves any of:
13	`vulnerability classes, buffer overflow, use-after-free, UAF, heap overflow, stack overflow, type confusion, integer overflow, format string, memory corruption, CVE case study, exploit development, Day 1-7`
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 1: Vulnerability Classes with Real-World Examples
29
30	## Course Overview
31
32	_created by AnotherOne from @Pwn3rzs Telegram channel_.
33
34	This document is Week 1 of a multi‑week exploit development course, focusing on core vulnerability classes and real‑world exploitation context.
35
36	Next Week we'll focus on using fuzzing to identify new vulnerabilites and in week 3 we'll focus on using patch diffing to find n-days
37
38	## Day 1: Memory Corruption Fundamentals
39
40	- Goal: Understand primary memory corruption vulnerability classes and their real-world impact.
41	- Activities:
42	- _Reading_:
43	- "The Art of Software Security Assessment" by Mark Dowd, John McDonald, Justin Schuh - Chapter 5: Memory Corruption
44	- [Memory Corruption: Examples, Impact, and 4 Ways to Prevent It](https://sternumiot.com/iot-blog/memory-corruption-examples-impact-and-4-ways-to-prevent-it/)
45	- _Online Resources_:
46	- [Microsoft Security Research: Memory Safety](https://www.microsoft.com/en-us/research/project/checked-c/)
47	- [Google Project Zero Blog](https://googleprojectzero.blogspot.com/) - Read recent memory corruption findings
48	- _Concepts_:
49	- What is memory corruption and why does it matter?
50	- Understanding the stack, heap, and their differences
51	- The lifecycle of memory: allocation → use → deallocation
52
53	### Stack Buffer Overflow
54
55	What It Is: A stack overflow occurs when a program writes more data to a buffer located on the stack than it can hold, causing adjacent memory to be overwritten. This can corrupt important data like return addresses, allowing attackers to redirect program execution.
56
57	Case Study - CVE-2024-27130 (QNAP QTS/QuTS hero Stack Overflow):
58
59	- The Bug: QNAP's QTS and QuTS hero operating systems contained multiple buffer copy vulnerabilities where unsafe functions like `strcpy()` were used to copy user-supplied input into fixed-size stack buffers without proper size validation. The vulnerabilities affected the web administration interface and file handling components. [POC](https://github.com/watchtowrlabs/CVE-2024-27130)
60	- The Attack: An authenticated remote attacker could send specially crafted requests with oversized input to vulnerable endpoints. The unchecked data would overflow stack buffers, corrupting adjacent memory including return addresses and saved frame pointers.
61	- The Impact: Remote code execution with the privileges of the QNAP system service. The attacker could gain complete control over the NAS device, accessing stored data, pivoting to other network resources, or installing persistent backdoors.
62	- The Fix: QNAP released QTS 5.1.7.2770 build 20240520 and QuTS hero h5.1.7.2770 build 20240520 in May 2024, replacing unsafe string copy functions with bounds-checked alternatives and implementing additional input validation.
63	- Why It Matters: Stack overflows remain common in embedded devices and NAS systems running legacy C/C++ code. They're particularly dangerous in internet-facing administration interfaces and often provide the initial foothold for sophisticated attack chains against enterprise infrastructure.
64
65	### Use-After-Free (UAF)
66
67	What It Is: A use-after-free vulnerability occurs when a program continues to use a pointer after the memory it points to has been freed. This creates a "dangling pointer" that can be exploited by carefully controlling heap allocations to place attacker-controlled data where the freed object once lived.
68
69	Case Study - CVE-2024-2883 (Chrome ANGLE Use-After-Free):
70
71	- The Bug: Google Chrome's ANGLE (Almost Native Graphics Layer Engine) component, which translates OpenGL ES API calls to DirectX, Vulkan, or native OpenGL, contained a use-after-free vulnerability. The bug

People who liked this also viewed

6 picks

Type

offensive-vuln-classes

2.8kstars447forks

View on GitHub

How to install offensive-vuln-classes?

snailsploit/claude-red/offensive-vuln-classes

$npx -y skills add SnailSploit/Claude-Red --skill offensive-vuln-classes

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# SKILL: Week 1: Vulnerability Classes with Real-World Examples
2
3	## Metadata
4	- Skill Name: vulnerability-classes
5	- Folder: offensive-vuln-classes
6	- Source: https://github.com/SnailSploit/offensive-checklist/blob/main/1-vulnerability-classes.md
7
8	## Description
9	Exploit development curriculum covering core vulnerability classes with real-world CVE case studies: stack/heap buffer overflows, use-after-free, integer overflows, format strings, type confusion, and race conditions. Use when learning or teaching vuln classes, researching specific CVE patterns, or building exploit dev knowledge.
10
11	## Trigger Phrases
12	Use this skill when the conversation involves any of:
13	`vulnerability classes, buffer overflow, use-after-free, UAF, heap overflow, stack overflow, type confusion, integer overflow, format string, memory corruption, CVE case study, exploit development, Day 1-7`
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 1: Vulnerability Classes with Real-World Examples
29
30	## Course Overview
31
32	_created by AnotherOne from @Pwn3rzs Telegram channel_.
33
34	This document is Week 1 of a multi‑week exploit development course, focusing on core vulnerability classes and real‑world exploitation context.
35
36	Next Week we'll focus on using fuzzing to identify new vulnerabilites and in week 3 we'll focus on using patch diffing to find n-days
37
38	## Day 1: Memory Corruption Fundamentals
39
40	- Goal: Understand primary memory corruption vulnerability classes and their real-world impact.
41	- Activities:
42	- _Reading_:
43	- "The Art of Software Security Assessment" by Mark Dowd, John McDonald, Justin Schuh - Chapter 5: Memory Corruption
44	- [Memory Corruption: Examples, Impact, and 4 Ways to Prevent It](https://sternumiot.com/iot-blog/memory-corruption-examples-impact-and-4-ways-to-prevent-it/)
45	- _Online Resources_:
46	- [Microsoft Security Research: Memory Safety](https://www.microsoft.com/en-us/research/project/checked-c/)
47	- [Google Project Zero Blog](https://googleprojectzero.blogspot.com/) - Read recent memory corruption findings
48	- _Concepts_:
49	- What is memory corruption and why does it matter?
50	- Understanding the stack, heap, and their differences
51	- The lifecycle of memory: allocation → use → deallocation
52
53	### Stack Buffer Overflow
54
55	What It Is: A stack overflow occurs when a program writes more data to a buffer located on the stack than it can hold, causing adjacent memory to be overwritten. This can corrupt important data like return addresses, allowing attackers to redirect program execution.
56
57	Case Study - CVE-2024-27130 (QNAP QTS/QuTS hero Stack Overflow):
58
59	- The Bug: QNAP's QTS and QuTS hero operating systems contained multiple buffer copy vulnerabilities where unsafe functions like `strcpy()` were used to copy user-supplied input into fixed-size stack buffers without proper size validation. The vulnerabilities affected the web administration interface and file handling components. [POC](https://github.com/watchtowrlabs/CVE-2024-27130)
60	- The Attack: An authenticated remote attacker could send specially crafted requests with oversized input to vulnerable endpoints. The unchecked data would overflow stack buffers, corrupting adjacent memory including return addresses and saved frame pointers.
61	- The Impact: Remote code execution with the privileges of the QNAP system service. The attacker could gain complete control over the NAS device, accessing stored data, pivoting to other network resources, or installing persistent backdoors.
62	- The Fix: QNAP released QTS 5.1.7.2770 build 20240520 and QuTS hero h5.1.7.2770 build 20240520 in May 2024, replacing unsafe string copy functions with bounds-checked alternatives and implementing additional input validation.
63	- Why It Matters: Stack overflows remain common in embedded devices and NAS systems running legacy C/C++ code. They're particularly dangerous in internet-facing administration interfaces and often provide the initial foothold for sophisticated attack chains against enterprise infrastructure.
64
65	### Use-After-Free (UAF)
66
67	What It Is: A use-after-free vulnerability occurs when a program continues to use a pointer after the memory it points to has been freed. This creates a "dangling pointer" that can be exploited by carefully controlling heap allocations to place attacker-controlled data where the freed object once lived.
68
69	Case Study - CVE-2024-2883 (Chrome ANGLE Use-After-Free):
70
71	- The Bug: Google Chrome's ANGLE (Almost Native Graphics Layer Engine) component, which translates OpenGL ES API calls to DirectX, Vulkan, or native OpenGL, contained a use-after-free vulnerability. The bug

People who liked this also viewed

6 picks

Type