Integrate Jazzer with Vulnesis. Fuzz Java libraries with coverage-guided mutations, then convert JVM crash findings to JSON for upload.
Install & scan
$ # Download the latest Jazzer release from GitHub curl -L https://github.com/CodeIntelligenceTesting/jazzer/releases/latest/download/jazzer_release.tar.gz -o jazzer.tar.gz && tar xzf jazzer.tar.gz # Or via Maven/Gradle (for JUnit 5 integration) # Maven: add com.code-intelligence:jazzer-junit:0.22.0 to test dependencies $ # Run Jazzer with a fuzz target class ./jazzer --cp=target/classes:target/dependency/* --target_class=com.example.FuzzTarget --instrumentation_includes=com.example.** corpus/
Run Jazzer in CI
Scan on every push and upload the report as a workflow artifact:
- name: Set up Java
uses: actions/setup-java@v4
with:
java-version: '17'
distribution: 'temurin'
- name: Build project
run: mvn package -DskipTests
- name: Download Jazzer
run: |
curl -L https://github.com/CodeIntelligenceTesting/jazzer/releases/latest/download/jazzer_release.tar.gz | tar xz
- name: Run Jazzer (5 minutes)
run: |
timeout 300 ./jazzer --cp=target/classes:target/dependency/* --target_class=com.example.FuzzTarget corpus/ || true
How Vulnesis compares: better together
Vulnesis does not replace Jazzer. Keep running it. Vulnesis sits on top of Jazzer (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
| Capability | Vulnesis | Jazzer |
|---|---|---|
| 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: coverage-guided JVM fuzzer on libFuzzer with JUnit 5 @FuzzTest and Java security sanitizers |
| 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 Jazzer does well
- Coverage-guided, in-process fuzzing for the JVM built on libFuzzer's mutation engine with JaCoCo-based LLVM-style edge-coverage instrumentation inserted at class load
- JUnit 5 integration via @FuzzTest so fuzz targets run alongside ordinary unit tests in regression or fuzzing mode
- Rich set of Java security bug detectors (sanitizers): SQL injection, unsafe deserialization/RCE, expression-language injection, LDAP injection, OS command injection, SSRF, file path traversal, regex injection, and JNDI/naming-context lookup (log4shell-class)
- Autofuzz mode can fuzz targets without hand-writing a harness
Where Vulnesis adds to it: Vulnesis has no native fuzzing engine and does not run JVM fuzzing itself; it ingests and orchestrates Jazzer's crash/sanitizer findings into one cross-scanner queue with EPSS/KEV/LEV exploit-intel prioritisation, versioned VEX and Safe Harbour autofix, so Jazzer keeps finding JVM bugs while Vulnesis triages and de-duplicates them alongside SAST/SCA/container results.
No migration, no rip-and-replace. Jazzer 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 Jazzer results in Vulnesis
Upload Jazzer 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.