Tool integration

Honggfuzz Integration Guide

Google's security-oriented feedback-driven fuzzer with hardware coverage

Get a Free API Key

Integrate Honggfuzz with Vulnetix. Fuzz C/C++ targets using software or hardware coverage, then convert crash findings to JSON for upload.

C / C++CLI toolJSON

Install & scan

$ # Build from source (Ubuntu)
sudo apt-get install -y build-essential binutils-dev libunwind-dev libblocksruntime-dev
git clone https://github.com/google/honggfuzz
cd honggfuzz && make && sudo cp honggfuzz /usr/local/bin/
$ # Step 1: Compile target with Honggfuzz instrumentation
./hfuzz_cc/hfuzz-clang -o target_hfuzz fuzz_target.c my_library.c

# Step 2: Run Honggfuzz
honggfuzz -i corpus/ -o findings/ -- ./target_hfuzz ___FILE___

Run Honggfuzz in CI

Scan on every push and upload the report as a workflow artifact:

- name: Build Honggfuzz and target
  run: |
    git clone --depth=1 https://github.com/google/honggfuzz
    cd honggfuzz && make
    ./hfuzz_cc/hfuzz-clang -o target_hfuzz ../fuzz_target.c

- name: Run Honggfuzz (60 seconds)
  run: |
    cd honggfuzz
    timeout 60 ./honggfuzz -i ../corpus/ -o ../findings/ -- ./target_hfuzz ___FILE___ || true

How Vulnetix compares: better together

Vulnetix does not replace Honggfuzz. Keep running it. Vulnetix sits on top of Honggfuzz (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.

CapabilityVulnetixHonggfuzz
Security coverage
SAST (static code analysis)✓ Built-in rules + Semgrep augmentation✗
SCA / dependencies✓ 40+ ecosystems, transitive graph✗
DAST (dynamic testing)~ Ingests DAST results; no native dynamic engine✗
Container & image✓ Image CVEs, base image, Dockerfile✗
IaC / misconfiguration✓ Terraform, k8s, CloudFormation✗
Secret scanning✓ 1,000+ rules, source + binary + git history✗
Cloud / CSPM✓ Cloud-posture findings, compliance tab✗
Mobile (MAST)~ Ingests mobile scanner output; no native mobile engine✗
License compliance✓ SPDX, copyleft/AGPL/SSPL policy✗
SBOM generation✓ CycloneDX 1.7 + SPDX 2.3, cosign-signable✗
Malware / supply-chain✓ De-duplicated corpus + install-time firewall (25+ registries)✗
Network / infra vuln~ Ingests network scanner output; no native network scanner✗
Fuzzing✗ Ingests fuzzing crashes; no native fuzzer✓ Feedback-driven, hardware-coverage-capable C/C++ fuzzer; its sole purpose.
Pentest / bug bounty✗ Ingests pentest/bug-bounty findings; not a testing service✗
The Vulnetix orchestration layer
Cross-scanner dedup & one queue (ASPM)✓ Correlates every scanner into one prioritised queue with ownership routing✗
Exploit-intel prioritisation✓ EPSS, CISA KEV, Coalition ESS, CWSS, Vulnetix LEV✗
Reachability analysis✓ Tree-sitter + CVEAffected; direct/transitive/semantic✗
Versioned VEX + audit trail✓ Immutable OpenVEX/CycloneDX, cosign-signable✗
Safe Harbour autofix✓ Resolves + applies the nearest safe version✗
End-of-life policy✓ Flags/blocks past-EOL runtimes & packages✗
SSVC / risk-based policy✓ SSVC v2 + CISA/FedRAMP/Essential-8 presets✗

✓ full · ~ partial · ✗ not covered

What Honggfuzz does well

Where Vulnetix adds to it: Vulnetix has no native fuzzing engine and does not run Honggfuzz; it ingests and orchestrates Honggfuzz crash output, consolidating it with scanner findings into one deduplicated, prioritised queue with exploit-intel, reachability, versioned VEX and Safe Harbour autofix. Better together: Honggfuzz surfaces the crashes, Vulnetix prioritises and drives them to fix.

No migration, no rip-and-replace. Honggfuzz keeps doing what it does best; Vulnetix adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today.

Centralise Honggfuzz results in Vulnetix

Upload Honggfuzz JSON output to the Vulnetix platform to deduplicate findings, prioritise them with EPSS, CISA KEV and Coalition ESS exploit intelligence, and track remediation across every scanner in a single queue.

Honggfuzz documentation ↗  ·  Source repository ↗

Wire Honggfuzz into your CI/CD pipeline →