'fuzzing' 검색 결과

Set up OSS-Fuzz for an open-source project and test it locally. Prepare configuration and build files, run fuzz tests that probe code with varied inputs, reproduce reported crashes, and inspect which code the tests reach.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing an open-source project for OSS-Fuzz enrollment
• Testing an OSS-Fuzz build locally before submission
• Reproducing crashes from OSS-Fuzz reports

Guides fuzz testing for Ruby libraries and gems with Ruzzy, using varied inputs to find failures. Covers pure Ruby and C extensions, including test harnesses, memory error detection, environment setup, and crash reproduction.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding fuzz tests to a Ruby library
• Testing memory safety in a gem's C extension
• Preparing tracer and harness scripts for pure Ruby

Set up libFuzzer to test C/C++ code with varied inputs guided by which code paths run. Build test harnesses, manage sample inputs and dictionaries, enable error detectors, and reproduce crashes or investigate stalled coverage.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Starting fuzz testing for a C/C++ library
• Writing or debugging an LLVMFuzzerTestOneInput harness
• Investigating runs that find no crashes or new code paths

Generate Echidna/Medusa-compatible Solidity fuzz suites from Foundry or Hardhat projects. Trigger on "fizz", "generate fuzz suite", "build fuzz harness", "stateful fuzzing", "fuzzing harness", "property testing", and "invariant suite".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Adaptive, targeted web fuzzing - deterministic wordlist selection (wl-pick.sh) plus judgment. Picks the right SecLists list per surface (content/vhost/api/params/artifacts) smallest-first, calibrates filters against soft-404s, recurses, escalates T0 harness -> T1 seclists -> T2 cewl -> T3 app-specific on signal, pivots to hidden-param fuzzing, and detects/handles WAF/Cloudflare/throttle (backoff, origin-bypass, or hard STOP on the DoS tell). Engagement-type aware (ctf loud, pt calibrated, bb stealth). Use for "fuzz", "content discovery", "directory brute", "vhost fuzz", "find hidden params", "which wordlist", "gobuster/ffuf/feroxbuster/cewl/arjun".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert guide for ephemeral WebAssembly (WASM) and isolated micro-runtime sandboxes to securely execute AI-generated code, validate database migrations in-memory, and perform sub-millisecond fuzzing / Panduan ahli sandbox WebAssembly (WASM) efemeral dan micro-runtime terisolasi untuk eksekusi kode AI yang aman, validasi migrasi database in-memory, dan fuzzing sub-milidetik.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AI-driven dynamic security fuzzing, exploit generation (XSS, SQLi, SSRF, Prompt Injection), and automated patch remediation / Fuzzing keamanan dinamis berbasis AI, eksploitasi, dan remediasi otomatis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Fuzzing with AFL++ for comprehensive binary and source code fuzzing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

API security testing and validation for REST/GraphQL/gRPC endpoints, contract testing, load testing, fuzzing, and Postman/Bruno/Hurl workflows

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when planning an end-to-end fuzzing program for a project: engine and target selection, corpus management, and CI or nightly wiring. Not for harness design: use fuzz-harness-writing. Not for engine operation or triage: use libfuzzer. Not for sanitizer flag reference: use sanitizers.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a parser, protocol, or file format fuzzer stalls at fixed-token validation gates and needs a coverage dictionary. Not for patching the SUT: use fuzzing-obstacles.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when asked to set up and run coverage-guided fuzzing of Ruby code or C extensions with Ruzzy, producing crash reports or clean campaign summaries. Not for C/C++ fuzzing: use libfuzzer or libfuzzer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Essential fuzzing payloads: SQL injection, command injection, special characters. Curated essentials for vulnerability testing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Systematically discover hidden Application Programming Interfaces (APIs), uncover undocumented endpoints (Shadow APIs), and fuzz parameters. Use this skill as the pivotal first step in API Bug Hunting, transforming a basic frontend application into a vast mapped attack surface.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guidelines and strategies for constructing meaningful test suites, property-based tests, metamorphic relations, and fuzzing harnesses. Trigger when: - Designing verification bounds, writing tests, creating test invariants, or implementing validation gates. - Prompt contains: testing, test design, property-based testing, PBT, metamorphic testing, fuzzing, integration tests, E2E.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide authorized security assessments of REST, SOAP, and GraphQL APIs. Organize endpoint discovery, authentication checks, access control tests, and input testing, then document discovered weaknesses and evidence of unauthorized data access.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Plan API checks for an authorized bug bounty assessment
• Check whether users can access another account's records
• Review GraphQL schema exposure and request limits

Review smart contract security through five steps covering Slither scans, special features, diagrams, documented safety conditions, and manual checks. Get project-specific findings, testing setup guidance, and a prioritized action plan for development or deployment reviews.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review smart contract security before deployment
• Triage Slither findings and false positives
• Visualize inheritance and access permissions

Writes, reviews, and debugs property-based tests, which generate inputs to check general rules. Helps test conversions, parsers, normalization, and state invariants, assess whether existing assertions are meaningful, and distinguish faulty rules from implementation bugs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Testing encode/decode round trips across generated inputs
• Checking normalization and sorting properties
• Reviewing whether existing property tests assert meaningful rules

Investigate TOCTOU flaws: race conditions where a checked property changes before an action uses it. The skill covers filesystem, kernel, web, and container testing, helping identify vulnerable sequences, reproduce timing issues, and document observed impact.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing file checks before privileged operations
• Testing access revocation during long-running requests
• Investigating duplicate payments from concurrent requests

Map a website’s exposed services by collecting subdomains, active hosts, and current or historical URLs. Inspect JavaScript and exposed files, prioritize areas for security testing, and monitor new subdomains and GitHub commits.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Mapping subdomains and active hosts
• Prioritizing API and authentication endpoints
• Inspecting JavaScript and exposed files

Discover subdomains, live hosts, and URLs to build a prioritized map for web security testing. Includes JavaScript analysis, API specification discovery, and monitoring for new subdomains, JavaScript changes, and GitHub commits.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building an inventory of web assets
• Prioritizing API and authentication endpoints
• Finding endpoints and secrets in JavaScript

This skill should be used when the user asks to "test API security", "fuzz APIs", "find IDOR vulnerabilities", "test REST API", "test GraphQL", "API penetration testing", "bug bounty API testing", or needs guidance on API security assessment techniques.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI, or debugging flaky/slow tests. For testify-specific APIs see `samber/cc-skills-golang@golang-stretchr-testify`; for measurement methodology see `samber/cc-skills-golang@golang-benchmark`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.