Skip to content
STIMSMITH

WhisperFuzz

Tool
First seen 8/5/2026
Last seen 8/5/2026
Evidence 20 chunks

NEIGHBORHOOD

No graph connections found for this entity yet. It may appear in future ingestion runs.

explore full graph →

RELATIONSHIPS

28 connections
Micro-Event Path uses → 100% 3e
WhisperFuzz uses Micro-Event Paths as timing coverage metrics and for vulnerability localization.
CVA6 evaluates → 100% 3e
WhisperFuzz is evaluated on the CVA6 processor, detecting new timing vulnerabilities.
Micro-Event Graph uses → 100% 3e
WhisperFuzz uses the Micro-Event Graph to capture microarchitectural transitions and localize timing vulnerabilities.
hardware fuzzing implements → 100% 2e
WhisperFuzz uses hardware fuzzing to explore processor design spaces.
static program analysis uses → 100% 2e
WhisperFuzz uses static program analysis to extract the Micro-Event Graph and identify root causes of vulnerabilities.
Register-Transfer Level uses → 100% 2e
WhisperFuzz extracts microarchitectural state transitions from a processor design at the register-transfer level.
simulation trace uses → 100% 2e
WhisperFuzz collects and analyzes simulation traces to detect and localize timing vulnerabilities.
hierarchical leakage analysis uses → 100% 2e
WhisperFuzz employs hierarchical leakage analysis to prioritize modules for timing vulnerability detection.
operand mutation uses → 100% 2e
WhisperFuzz uses operand mutation to generate data-dependent inputs for timing vulnerability detection.
SystemVerilog Assertion uses → 100% 2e
WhisperFuzz converts MEPs into SystemVerilog Assertion cover properties to monitor timing coverage.
timing coverage metric uses → 100% 2e
WhisperFuzz introduces and uses a timing coverage metric to evaluate timing behaviors explored.
Directed Fuzzing implements → 95% 2e
WhisperFuzz is a directed fuzzer targeting data-dependent timing channels.
register dependency uses → 90% 2e
WhisperFuzz relies on register dependencies for its leakage analysis.
White-Box Fuzzing implements → 100% 2e
WhisperFuzz is a white-box fuzzer implementing white-box fuzzing techniques for hardware.
seed generation uses → 100% 2e
WhisperFuzz has a seed generation module that produces initial instruction sequences for fuzzing.
Instruction Sequence Generation uses → 100% 2e
WhisperFuzz generates instruction sequences as test inputs to detect timing vulnerabilities.
Design Under Test uses → 100% 2e
WhisperFuzz instruments and simulates the design-under-test to detect timing vulnerabilities.
BOOM evaluates → 100% 2e
WhisperFuzz is evaluated on the BOOM processor, detecting new timing vulnerabilities.
Rocket Core evaluates → 100% 2e
WhisperFuzz is evaluated on the Rocket Core processor, detecting new timing vulnerabilities.
Black-Box Fuzzing ← compares with 90% 2e
WhisperFuzz is compared with black-box fuzzing approaches that cannot locate timing vulnerability root causes.
Grey-Box Fuzzing ← compares with 90% 2e
WhisperFuzz is compared with grey-box fuzzing approaches that cannot locate timing vulnerability root causes.
coverage-feedback fuzzing uses → 100% 1e
WhisperFuzz uses a coverage-feedback fuzzer in its seed generation module.
Chipyard uses → 100% 1e
WhisperFuzz uses the Chipyard environment for processor evaluation.
The paper introduces WhisperFuzz as its primary contribution.
Differential Testing uses → 90% 1e
WhisperFuzz uses differential testing by comparing simulation traces to detect timing vulnerabilities.
breadth-first search uses → 100% 1e
WhisperFuzz's Diagnozer uses breadth-first search to trace combinational signals to sequential elements.
HyPFuzz uses → 100% 1e
WhisperFuzz uses HyPFuzz to generate seeds for its Operand mutator.
VCS uses → 100% 1e
WhisperFuzz uses VCS to collect coverage reports and simulation traces.