Grant: Discovery Grants Program - Individual
The University of British Columbia
$36,000.00
Fuzz-Driven Development
EF 2024-25
Résumé
Software bugs remain pervasive in modern software systems. Broadly defined, a software bug occurs when there is a gap between what the software was intended to do, and what the implementation of the software actually does. The consequences of software bugs can range from annoyances (e.g., a messaging app crashing), to severe security vulnerabilities (e.g., enabling attackers to steal credit card information). Bugs also have severe financial costs, illustrated by the fact that companies like Google and Amazon are willing to offer over $10,000 to analysts who discover critical bugs in their systems.
Shortening the time between bug introduction and fixing mitigates the worst impacts of bugs. If a developer finds a bug five minutes after its introduction, it will be fixed before the software is released to end-users: any consequences related to the bug are averted. The long-term goal of my research agenda is to build tools that allow software developers to reduce the time between bug introduction and fixing to minutes, rather than hours, days, or months.
Before a bug is fixed, it must be discovered. A popular method for rapid bug discovery is fuzz testing. Fuzz testing refers to a suite of techniques that use automated random search to generate inputs, send these inputs to the program, and observe the behaviour of the program in response. Fuzz testing monitors whether the program crashes on any generated input, typically indicative of a bug in the program. These concrete crashing inputs serve as reproducible test cases, the gold standard for identifying and fixing bugs.
Fuzz testing has discovered tens of thousands of software bugs. The discovery and repair of such bugs has helped avert many crises. For instance, fuzz testing quickly discovered a bug in the software used to secure internet communication, which would have allowed attackers to execute arbitrary code on a user's computer. This bug was quickly fixed before the software was adopted by users.
However, fuzz testing is still largely confined to a quality assurance step, run for hours, days, or months on one version of a program. Further, it is only run on the limited range of software systems on which it is easy to set up. The short-term objective of my research program is to reap the rewards of fuzz testing more broadly by making fuzz testing a first-class development activity. I will accomplish this by making fuzz testing (1) adaptive to programs with evolving input models, (2) interactive to developer intent, and (3) transparent, so developers can use fuzz testing as efficiently as possible.
The direct impacts of my research program will enable more developers to use fuzz testing during software development, reducing the time between bug introduction and discovery to minutes. The broader impacts of my research program will reduce the number of bugs that make it to software used by end-users, increasing the reliability, security, and safety of the software that powers our society.
Programme
Discovery Grants Program - Individual
Bénéficiaire
Emplacement
British Columbia, Canada
Type de bénéficiaire
Academia
Type
Grant
Source
NSERC's Awards Data
Tel que publié
Application id
RGPIN-2023-04478
Name nom
Lemieux, Caroline
Department département
Computer Science
Organization id
2
Institution établissement
The University of British Columbia
Province en
British Columbia
Province fr
Colombie-Britannique
Country en
CANADA
Country fr
CANADA
Fiscal year exercice financier
2024
Competition year année de concours
2023
Award amount
36000
Program id
RGPIN
Program name en
Discovery Grants Program - Individual
Program name fr
Programme de subventions à la découverte - individuelles
Group en
DISCOVERY RESEARCH
Group fr
RECHERCHE AXÉE SUR LA DÉCOUVERTE
Committee code
1507
Committee name en
Computer Science
Committee name fr
Sciences informatiques
Area of application code
802
Area of application group en
Information and communication services
Area of application group fr
Services d'information et de télécommunications
Area of application en
Information systems and technology
Area of application fr
Systèmes d'information et technologie de l'information
Research subject code
2706
Research subject group en
Information technology
Research subject group fr
Technologie de l'information
Research subject en
Software engineering
Research subject fr
Génie logiciel
Field of research list names en
Not available
Field of research list names fr
Non disponible
Socioeconomic objective list names en
Not available
Socioeconomic objective list names fr
Non disponible
Application title
Fuzz-Driven Development
Keywords
fuzz testing; software testing; program analysis; bug detection; security testing
Application summary
Software bugs remain pervasive in modern software systems. Broadly defined, a software bug occurs when there is a gap between what the software was intended to do, and what the implementation of the software actually does. The consequences of software bugs can range from annoyances (e.g., a messaging app crashing), to severe security vulnerabilities (e.g., enabling attackers to steal credit card information). Bugs also have severe financial costs, illustrated by the fact that companies like Google and Amazon are willing to offer over $10,000 to analysts who discover critical bugs in their systems.
Shortening the time between bug introduction and fixing mitigates the worst impacts of bugs. If a developer finds a bug five minutes after its introduction, it will be fixed before the software is released to end-users: any consequences related to the bug are averted. The long-term goal of my research agenda is to build tools that allow software developers to reduce the time between bug introduction and fixing to minutes, rather than hours, days, or months.
Before a bug is fixed, it must be discovered. A popular method for rapid bug discovery is fuzz testing. Fuzz testing refers to a suite of techniques that use automated random search to generate inputs, send these inputs to the program, and observe the behaviour of the program in response. Fuzz testing monitors whether the program crashes on any generated input, typically indicative of a bug in the program. These concrete crashing inputs serve as reproducible test cases, the gold standard for identifying and fixing bugs.
Fuzz testing has discovered tens of thousands of software bugs. The discovery and repair of such bugs has helped avert many crises. For instance, fuzz testing quickly discovered a bug in the software used to secure internet communication, which would have allowed attackers to execute arbitrary code on a user's computer. This bug was quickly fixed before the software was adopted by users.
However, fuzz testing is still largely confined to a quality assurance step, run for hours, days, or months on one version of a program. Further, it is only run on the limited range of software systems on which it is easy to set up. The short-term objective of my research program is to reap the rewards of fuzz testing more broadly by making fuzz testing a first-class development activity. I will accomplish this by making fuzz testing (1) adaptive to programs with evolving input models, (2) interactive to developer intent, and (3) transparent, so developers can use fuzz testing as efficiently as possible.
The direct impacts of my research program will enable more developers to use fuzz testing during software development, reducing the time between bug introduction and discovery to minutes. The broader impacts of my research program will reduce the number of bugs that make it to software used by end-users, increasing the reliability, security, and safety of the software that powers our society.