FuSeBMC: An Energy-Efficient Test Generator for Finding Security Vulnerabilities in C Programs

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

We describe and evaluate a novel approach FuSeBMC that exploits fuzzing and BMC engines to detect security vulnerability in C programs. It explores and analyzes the target C program by injecting labels that guide those engines to produce test-cases. FuSeBMC also exploits selective fuzzer to produce test-cases for the labels that fuzzing and BMC engines could not produce test-cases. Lastly, we manage each engine's execution time to improve FuSeBMC's energy consumption. As a result, FuSeBMC guides the fuzzing and BMC engines to explore more profound in the target C programs and then produce test-cases that achieve higher coverage with lower energy consumption to detect bugs efficiently. We evaluated FuSeBMC by participating in Test-Comp 2021 to test the ability of the tool in two categories of the competition, which are code coverage and bug detection. The competition results show that FuSeBMC performs well if compared to the state-of-the-art software testing tools. FuSeBMC achieved 3 awards in the Test-Comp 2021: first place in the Cover-Error category, second place in the Overall category, and third place in the Low Energy Consumption.
Original languageEnglish
Title of host publicationTAP: International Conference on Tests and Proofs
PublisherSpringer London
Publication statusPublished - 18 Jun 2021
Event15th International Conference on Tests and Proofs - Bergen, Norway
Duration: 21 Jun 202125 Jun 2021

Publication series

NameLecture Notes in Computer Science
PublisherSpringer

Conference

Conference15th International Conference on Tests and Proofs
Abbreviated titleTAP 2021
Country/TerritoryNorway
CityBergen
Period21/06/2125/06/21

Fingerprint

Dive into the research topics of 'FuSeBMC: An Energy-Efficient Test Generator for Finding Security Vulnerabilities in C Programs'. Together they form a unique fingerprint.

Cite this