Tool integration

Boofuzz integration guide

Network protocol fuzzer: fuzz any TCP/UDP/serial protocol with Python

Get a Free API Key

Integrate Boofuzz with Vulnesis. Fuzz network protocols to discover crashes and unexpected responses, then convert findings to JSON for upload.

Python / Network ProtocolsCLI toolJSON

Install & scan

$ # Recommended: ephemeral environment
uv run --with boofuzz python3 -c "import boofuzz; print(boofuzz.__version__)"

# Or install globally
pip install boofuzz
$ # Run the fuzz script
uv run --with boofuzz python3 fuzz_protocol.py

Run Boofuzz in CI

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

- name: Install Boofuzz
  run: pip install boofuzz

- name: Start target service
  run: ./target_server &

- name: Run Boofuzz (10 minutes)
  run: timeout 600 python3 fuzz_protocol.py || true

- name: Export crashes
  run: python3 export_crashes.py

- name: Upload to Vulnesis
  run: vulnetix upload --file boofuzz-crashes.json

How Vulnesis compares: better together

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

CapabilityVulnesisBoofuzz
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✓ Core: generation-based network protocol fuzzer with target monitoring, reset and crash recording
Pentest / bug bounty✗ Ingests pentest/bug-bounty findings; not a testing service✗
The Vulnesis 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, Vulnesis 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 Boofuzz does well

Where Vulnesis adds to it: Vulnesis runs no network fuzzing and does not model or send protocol test cases; it ingests Boofuzz crash/failure records and orchestrates them into one prioritised queue with exploit-intel, VEX and SSVC policy. Boofuzz drives the protocol testing against live targets; Vulnesis consolidates and prioritises what it surfaces alongside all other scanner output.

No migration, no rip-and-replace. Boofuzz keeps doing what it does best; Vulnesis adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today. Software Factory agents on a Pix Sandbox can then turn the findings from any scanner into pull requests that a person approves. How Software Factory works.

Centralise Boofuzz results in Vulnesis

Upload Boofuzz JSON output to the Vulnesis 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.

Boofuzz documentation ↗  ·  Source repository ↗

Wire Boofuzz into your CI/CD pipeline →