Community코딩 & 개발github.com

trailofbits/ossfuzz

OSS-Fuzz는 오픈소스 프로젝트에 무료 지속적 퍼징을 제공합니다. 지속적 퍼징 인프라를 설정하거나 프로젝트를 등록할 때 사용하세요.

ossfuzz란 무엇인가요?

이 스킬은 오픈소스 프로젝트에 무료로 지속적인 퍼징(continuous fuzzing) 서비스를 제공하는 OSS-Fuzz를 설정하고 활용하는 방법을 안내합니다. 주로 C/C++, Go, Rust, Python, Java 등 다양한 언어로 작성된 오픈소스 프로젝트에서 보안 취약점과 버그를 자동으로 발견하는 데 사용됩니다. 사용자는 프로젝트 저장소에 퍼징 타겟(fuzzing targets)을 추가하고, OSS-Fuzz 인프라에 등록하여 자동화된 버그 탐지 및 리포트를 받을 수 있습니다. 이 스킬은 지속적 통합(CI) 환경과 통합되어 안정적인 퍼징 파이프라인을 구축하고, 발견된 이슈를 개발자에게 알리는 워크플로우를 지원합니다.

지원 대상~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/trailofbits/skills/tree/main/skills/ossfuzz

Installed? Explore more 코딩 & 개발 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

문서

ossfuzz은(는) 무엇을 하나요?

OSS-Fuzz는 오픈소스 프로젝트에 무료 지속적 퍼징을 제공합니다. 지속적 퍼징 인프라를 설정하거나 프로젝트를 등록할 때 사용하세요.

개요

OSS-Fuzz는 Google이 운영하는 서비스로, 중요한 오픈소스 소프트웨어에서 보안 취약점을 찾기 위해 지속적인 퍼징을 제공합니다. 이 스킬은 프로젝트를 OSS-Fuzz에 등록하고 퍼징 인프라를 구성하는 과정을 안내합니다.

지원 언어

  • C/C++ (libFuzzer, AFL, Honggfuzz)
  • Go (go-fuzz)
  • Rust (cargo-fuzz)
  • Python (Atheris)
  • Java (Jazzer)

사전 요구 사항

  • GitHub 또는 GitLab에 호스팅된 오픈소스 프로젝트
  • OSI 승인 오픈소스 라이선스
  • 프로젝트 관리자의 등록 동의

시작하기

1단계: 퍼징 타겟 추가

프로젝트 저장소에 퍼징 테스트를 추가합니다. 예를 들어, C++ 프로젝트의 경우:

#include <stdint.h>
#include <stddef.h>

extern "C" int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
  // 퍼징할 코드 호출
  MyFunction(data, size);
  return 0;
}

2단계: Dockerfile 생성

OSS-Fuzz는 Docker를 사용하여 빌드 환경을 격리합니다. 프로젝트 루트에 Dockerfile을 생성합니다:

FROM gcr.io/oss-fuzz-base/base-builder
RUN apt-get update && apt-get install -y make autoconf automake libtool
COPY . $SRC/project
WORKDIR $SRC/project
COPY build.sh $SRC/

3단계: build.sh 스크립트 작성

build.sh 파일을 생성하여 퍼저를 컴파일합니다:

#!/bin/bash -eu

cd $SRC/project
make

$CXX $CXXFLAGS -std=c++11 -I. \
    $SRC/project/fuzz_target.cc \
    -o $OUT/fuzz_target \
    $LIB_FUZZING_ENGINE \
    $SRC/project/lib/lib.a

4단계: 프로젝트 등록

projects/ 디렉토리에 project.yaml 파일을 추가합니다:

homepage: "https://project-website.example.com"
language: c++
primary_contact: "[email protected]"
auto_ccs:
  - "[email protected]"

5단계: 테스트 및 제출

로컬에서 퍼징을 테스트합니다:

docker run -it --rm --privileged \
  -v $(pwd):/workspace \
  gcr.io/oss-fuzz-base/base-runner \
  /workspace/fuzz_target

이상이 없으면 OSS-Fuzz 저장소에 풀 리퀘스트를 보냅니다.

추가 리소스

라이선스

Apache 2.0

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

trailofbits/address-sanitizer

AddressSanitizer detects memory errors during fuzzing. Use when fuzzing C/C++ code to find buffer overflows and use-after-free bugs.

trailofbits/aflpp

AFL++ is a fork of AFL with better fuzzing performance and advanced features. Use for multi-core fuzzing of C/C++ projects.

trailofbits/agentic-actions-auditor

Audits GitHub Actions workflows for security vulnerabilities in AI agent integrations including Claude Code Action, Gemini CLI, OpenAI Codex, and GitHub AI Inference. Detects attack vectors where attacker-controlled input reaches AI agents running in CI/CD pipelines, including env var intermediary patterns, direct expression injection, dangerous sandbox configurations, and wildcard user allowlists. Use when reviewing workflow files that invoke AI coding agents, auditing CI/CD pipeline security for prompt injection risks, or evaluating agentic action configurations.

trailofbits/algorand-vulnerability-scanner

Scans Algorand smart contracts for 11 common vulnerabilities including rekeying attacks, unchecked transaction fees, missing field validations, and access control issues. Use when auditing Algorand projects (TEAL/PyTeal).

trailofbits/ask-questions-if-underspecified

Clarify requirements before implementing. Use when serious doubts arise.

trailofbits/atheris

Atheris is a coverage-guided Python fuzzer based on libFuzzer. Use for fuzzing pure Python code and Python C extensions.

trailofbits/audit-augmentation

Augments Trailmark code graphs with external audit findings from SARIF static analysis results and weAudit annotation files. Maps findings to graph nodes by file and line overlap, creates severity-based subgraphs, and enables cross-referencing findings with pre-analysis data (blast radius, taint, etc.). Use when projecting SARIF results onto a code graph, overlaying weAudit annotations, cross-referencing Semgrep or CodeQL findings with call graph data, or visualizing audit findings in the context of code structure.

trailofbits/audit-context-building

Enables ultra-granular, line-by-line code analysis to build deep architectural context before vulnerability or bug finding.

trailofbits/audit-prep-assistant

Prepares codebases for security review using Trail of Bits' checklist. Helps set review goals, runs static analysis tools, increases test coverage, removes dead code, ensures accessibility, and generates documentation (flowcharts, user stories, inline comments).

trailofbits/burpsuite-project-parser

Searches and explores Burp Suite project files (.burp) from the command line. Use when searching response headers or bodies with regex patterns, extracting security audit findings, dumping proxy history or site map data, or analyzing HTTP traffic captured in a Burp project.

trailofbits/cairo-vulnerability-scanner

Scans Cairo/StarkNet smart contracts for 6 critical vulnerabilities including felt252 arithmetic overflow, L1-L2 messaging issues, address conversion problems, and signature replay. Use when auditing StarkNet projects.

trailofbits/cargo-fuzz

cargo-fuzz is the de facto fuzzing tool for Rust projects using Cargo. Use for fuzzing Rust code with libFuzzer backend.

trailofbits/chrome-mcp-troubleshooting

Diagnose and fix Claude in Chrome MCP extension connectivity issues. Use when mcp__claude-in-chrome__* tools fail, return "Browser extension is not connected", or behave erratically.

trailofbits/claude-in-chrome-troubleshooting

Diagnose and fix Claude in Chrome MCP extension connectivity issues. Use when mcp__claude-in-chrome__* tools fail, return "Browser extension is not connected", or behave erratically.

trailofbits/code-improver

Runs an autonomous review-and-fix improvement loop over any code target — a skill, plugin, module, or directory — using a reviewer the user names: any installed skill or agent. Keeps a cross-round findings ledger, escalates when fixes stop converging, and guards scope mechanically. Use when asked to 'improve this code until review passes', 'run an improvement loop with <reviewer>', or to iterate review-and-fix with a specific reviewer. For skills prefer the skill-improver entry; for a branch prefer pr-improver.

trailofbits/code-maturity-assessor

Systematic code maturity assessment using Trail of Bits' 9-category framework. Analyzes codebase for arithmetic safety, auditing practices, access controls, complexity, decentralization, documentation, MEV risks, low-level code, and testing. Produces professional scorecard with evidence-based ratings and actionable recommendations.

trailofbits/codeql

Scans a codebase for security vulnerabilities using CodeQL's interprocedural data flow and taint tracking analysis. Triggers on "run codeql", "codeql scan", "codeql analysis", "build codeql database", or "find vulnerabilities with codeql". Supports "run all" (security-and-quality + security-experimental suites) and "important only" (high-precision security findings) scan modes. Also handles creating data extension models and processing CodeQL SARIF output.

trailofbits/constant-time-analysis

Detects timing side-channel vulnerabilities in cryptographic code. Use when implementing or reviewing crypto code, encountering division on secrets, secret-dependent branches, or constant-time programming questions in C, C++, Go, Rust, Swift, Java, Kotlin, C#, PHP, JavaScript, TypeScript, Python, or Ruby.

trailofbits/constant-time-testing

Constant-time testing detects timing side channels in cryptographic code. Use when auditing crypto implementations for timing vulnerabilities.

trailofbits/cosmos-vulnerability-scanner

Scans Cosmos SDK blockchain modules and CosmWasm contracts for consensus-critical vulnerabilities — chain halts, fund loss, state divergence. 25 core + 16 IBC + 10 EVM + 3 CosmWasm patterns. Use when auditing custom x/ modules, reviewing IBC integrations, or assessing pre-launch chain security. Updated for SDK v0.53.x.

관련 스킬