- Home
- Fuzz Testing Software
- Metalware
On the recordRead 7 Oct 202624 facts
Metalware
On the record
- Analysis duration
- The default analysis duration is 24 hours and can be configured from the dashboard.metalware.com · read 7 Oct 2026
- Analysis output
- Defect details include root cause analysis, a stack trace, and a reproducible proof-of-concept input.metalware.com · read 7 Oct 2026
- Analysis results
- Defects include a stack trace, root cause analysis, and proof-of-concept input, and can be reproduced with time-travel debugging.metalware.com · read 7 Oct 2026
- CI/CD integrations
- The maker documents GitHub Actions and GitLab CI workflows, with options to file discovered defects as GitHub or GitLab issues.metalware.com · read 7 Oct 2026
- Company
- The company site identifies the maker as Metalware Inc.; LinkedIn lists its headquarters as San Francisco, California, and its founding year as 2023.linkedin.com · read 7 Oct 2026
- Debugger integrations
- Metalware provides Ghidra and Binary Ninja plugins and remote GDB for investigating defects.metalware.com · read 7 Oct 2026
- Debugging integrations
- Metalware provides debugging through Ghidra and Binary Ninja plugins and remote GDB.metalware.com · read 7 Oct 2026
- Deployment
- Metalware is available as a cloud service or on-premise deployment; the on-premise instructions require a modern Linux computer with Docker.metalware.com · read 7 Oct 2026
- Emulation
- It runs firmware on an emulated ARM Cortex-M processor and models peripheral I/O without physical hardware.metalware.com · read 7 Oct 2026
- Emulation and fuzzing
- Metalware emulates an ARM Cortex-M processor, models memory-mapped peripheral I/O, automatically detects DMA buffers, and uses coverage-guided fuzzing.metalware.com · read 7 Oct 2026
- Fuzzing
- Its coverage-guided fuzzer tracks basic blocks, keeps inputs that reach new code, and mutates them to explore further.metalware.com · read 7 Oct 2026
- Input requirements
- Metalware supports ELF and raw .bin binaries for ARM Cortex-M firmware, and debug symbols are not required.metalware.com · read 7 Oct 2026
- Inputs
- It accepts firmware ELF files, ROMs, binary images, update blobs, and extracted components, with a device or board profile and optional symbols or metadata.product.metalware.com · read 7 Oct 2026
- Intended users
- The maker describes use by product security teams, DevSecOps, reverse engineers and vulnerability researchers, and firmware engineers.product.metalware.com · read 7 Oct 2026
- Issue tracking
- The CLI can automatically file newly discovered defects as GitHub or GitLab issues and deduplicates previously filed issues.metalware.com · read 7 Oct 2026
- No hardware or source
- The maker says analysis runs without physical hardware or source code, and requires no test harness.metalware.com · read 7 Oct 2026
- Notable limits
- The docs specify support for ARM Cortex-M firmware and say on-premise fuzzing is CPU intensive, with performance scaling linearly with core count.metalware.com · read 7 Oct 2026
- On-premise requirements
- The on-premise documentation says a modern Linux computer with Docker should work and that fuzzing is CPU intensive, with performance scaling linearly with core count.metalware.com · read 7 Oct 2026
