find-bugs

Identify memory-safety and exploitation risks in C/C++ codebases.

1|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/dcbz/exploit_skillz --skill find-bugs-dcbz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-bugs
Source: https://github.com/dcbz/exploit_skillz/tree/main/find-bugs
Command: npx skills add https://github.com/dcbz/exploit_skillz --skill find-bugs-dcbz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify memory-safety vulnerabilities and exploitation opportunities in C/C++ codebases to enable thorough security audits and risk assessment.

Core Features & Use Cases

  • Structured nine-step framework to map trust boundaries, data flow, parsing logic, and heap/stack usage.
  • Guided analysis of memory corruption vectors, concurrency issues, and exploitability paths.
  • Applicable to security assessments, vulnerability research, and zero-day analysis across complex codebases.

Quick Start

Apply the 9-step vulnerability research workflow to your C/C++ codebase to systematically identify memory-safety risks and exploitable paths.

Frequently Asked Questions about find-bugs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify memory-safety vulnerabilities in a C/C++ codebase?

Memory-safety vulnerabilities in C/C++ are identified by applying a structured nine-step framework that maps trust boundaries, data flow, parsing logic, and heap/stack usage. This systematic approach traces exploitable paths to ensure comprehensive risk assessment across complex codebases.

What is data-flow tracing for vulnerability research?

Data-flow tracing for vulnerability research is a structured reasoning process that maps how input is handled and parsed across trust boundaries. It helps systematically uncover memory corruption, information disclosure, denial of service, and remote code execution scenarios in complex codepaths.

How do I assess exploitability paths for memory corruption during a code audit?

You assess exploitability paths by following guided analysis of memory corruption vectors and concurrency issues. This involves step-by-step data-flow tracing across heap and stack usage to determine if memory-safety risks can be leveraged for remote code execution.

Can I use this structured analysis for zero-day analysis on large codepaths?

Yes, this systematic security audit framework is explicitly designed for zero-day analysis across large or complex codepaths. It focuses deeply on input handling, parsing, concurrency, and heap/stack usage to uncover hidden remote code execution and denial of service risks.

What is the best way to find concurrency issues during a C/C++ security audit?

The best way to find concurrency issues is to apply a systematic nine-step vulnerability research workflow. It includes guided analysis of concurrency issues alongside memory corruption vectors to comprehensively evaluate exploitation opportunities and denial of service scenarios.