Evaluating the maintainability of Forward-Porting vulnerabilities in fuzzer benchmarks

Before Migration: all files are available at https://osf.io/xnejq/?view_only=9d23901bf9d04cd4968c70e950d4f95f

Launch Instruction

bash ./docker_tools/launch_one_version.sh CVEs/config_file_cve-yyy-xxxx commit_tag fp_flag 

Arguments:

config_file_cve-yyy-xxxx – path to the CVE-specific configuration (e.g., CVEs/config_file_cve-yyy-xxxx).
Commit tag – project version or tag to build (e.g., v1.6.40).
Forward-Porting flag - (Optional) 0 = no, 1 = yes, default = 0. 

Repository Structure

│
│── CVEs/
│   ├── config_file_cve-2019-7317
│   └── optional_prebuild_options_*
│── docker_tools/
│   ├── launch_full-auto-maintained_fp_one_cve_docker.sh
│   ├── Dockerfile_<project>       # per-project templates
│   └── docker_images/             # generated build contexts
│
|── Evolution_Figure
│
│── Forward_Patches/
│   └── CVE-XXXX-YYYY/
│       ├── <commit_tag>_*
│       └── maintain/
│
│── misc
│
│── PoCs/
│   └── CVE-XXXX-YYYY/
|
│── Projects/
│   ├── config_file_<project>
│   ├── make_file_<project>
│   └── pkg_dependencies_<project>
|	
│── Target_Libraries
|
└── README.md		

Link to the paper

</td>