{"id":2094,"date":"2009-09-14T10:21:31","date_gmt":"2009-09-14T10:21:31","guid":{"rendered":"https:\/\/www.darknet.org.uk\/?p=2094"},"modified":"2015-09-09T19:37:55","modified_gmt":"2015-09-09T11:37:55","slug":"4f-the-file-format-fuzzing-framework","status":"publish","type":"post","link":"https:\/\/www.darknet.org.uk\/2009\/09\/4f-the-file-format-fuzzing-framework\/","title":{"rendered":"4f: The File Format Fuzzing Framework"},"content":{"rendered":"

4f is a file format fuzzing framework<\/a>. 4f uses modules which are specifications of the targeted binary or text file format that tell it how to fuzz the target application. If 4f detects a crash, it will log crucial information important for allowing the 4f user to reproduce the problem and also debugging information important to deciding the severity of the bug and its exploitability.<\/p>\n

4f’s purpose is to find vulnerabilities in code that parses file formats including configuration files.<\/p>\n

4f uses specialized modules for fuzzing code that interprets file formats. Several modules are included and more can be written to follow other file formats.<\/p>\n

A module system is in place for fuzzing any file format you like as long as you know its specification<\/p>\n

Custom debugger gathers crucial debugging information on crash, logs it, then continues fuzzing.<\/p>\n

Usage<\/strong><\/p>\n