How ernw/dizzy works
Main Components Identification
The system should be represented with these key components:
a) Core Engine Components:
• Fuzzing Engine (dizz.py, dizz_state.py)
• Interaction Engine (interaction.py, interaction_state.py)
• Job Controller (job.py)
• Configuration Manager (config.py)
b) Module System:
• Module Loader (module.py)
• Library Manager (library.py)
c) Functional Components:
• Encodings System (/encodings)
• Functions System (/functions)
• Objects System (/objects)
• Session Handlers (/session)
• Probes System (/probe)
Component Relationships
[Job Controller]
• ► [Configuration Manager]
• ► [Fuzzing Engine] ◄─────────┐
• ▼ │
• [Objects System] │
• ▼ │
• [Functions System] │
• ► [Interaction Engine] ──────┘
• ▼
• [Session Handlers]
• ▼
• ► [Probes System]
[Module Loader] ───► [Library Manager]
Component Details
Annotations for each major component:
a) Core Engine:
• Fuzzing Engine: Handles packet mutation and fuzzing logic
• Interaction Engine: Manages state-full fuzzing sequences
• Job Controller: Orchestrates fuzzing jobs and workflow
b) Module System:
• Module Loader: Handles dynamic loading of fuzzing modules
• Library Manager: Manages shared resources and dependencies
c) I/O Components:
• Session Handlers: Multiple protocol support (TCP, UDP, HTTP, etc.)
• Probes: Target monitoring and availability checking
Implementation Notes
Technical details:
• Python-based implementation
• Modular architecture
• Support for both state-full and state-less fuzzing
• Multiple protocol support
• Extensible plugin system
• The central role of the Job Controller
• The separation between fuzzing and interaction engines
• The modularity of the session and probe systems
• The extensibility through the module system
This design captures the framework's ability to handle both state-full and state-less fuzzing while maintaining a clean separation of concerns between different components.