Automated Exploit and Security Test Generation: A Systematic Literature Review
summary
The gist
A Systematic Literature Review on Automated Exploit and Security Test Generation surveys existing techniques for automatically generating exploits and security tests for software vulnerabilities to…
In short
This systematic review surveyed existing methods for automatically creating software exploits and security tests to help researchers understand their characteristics. It categorized techniques into automated generation, testing, fuzzing, and others, noting that control-flow hijacking is dominant in exploit generation.
Key concepts
- Automated Exploit Generation (AEG)
- Techniques designed to automatically create working exploits or Proof of Concept code for software vulnerabilities. The goal is to reduce the time and expert knowledge needed to craft these malicious payloads.
- Security Testing
- A broad category of methods used to verify software security, including model-based, logic programming, and heuristic testing. These methods aim to find flaws in applications before they can be exploited by attackers.
- Fuzzing
- A technique where random or semi-random inputs are fed into a program to discover unexpected behavior or vulnerabilities. Coverage-based greybox fuzzing is highlighted as a prominent method within this category.
- Control-flow Hijacking
- A dominant automated exploit generation technique identified in the survey. It involves manipulating the program's execution flow by redirecting where the CPU goes next, often used to achieve arbitrary code execution in memory-based vulnerabilities.
Terminology used across episodes
This episode discusses
- Automated Exploit and Security Test Generation: A Systematic Literature Review · Paper Radio
- VulDeePecker: A Deep Learning-Based System for Vulnerability Detection
The paper
Automated Exploit and Security Test Generation: A Systematic Literature Review · Read on arXiv
QUANG-CUONG BUI, EMANUELE IANNONE, MARIA CAMPORESE, TORGE HINRICHS, CATHERINE TONY, LÁSZLÓ TÓTH, FABIO PALOMBA, PÉTER HEGEDŰS, FABIO MASSACCI, RICCARDO SCANDARIATO
Hamburg University of Technology · University of Trento · University of Szeged
Static analysis techniques are often insufficient to determine whether a reported security vulnerability is exploitable and actually poses a real security risk to a software application. Dynamic analysis addresses this limitation by executing the target application with carefully crafted inputs that trigger or reproduce a given vulnerability. Over the past two decades, automatic exploit generation (AEG) and automatic security test generation (ASTG) have emerged as active research areas in cybersecurity and software engineering. This paper demystifies the field by establishing consistent terminology and presenting a systematic literature review (SLR) of research published in the last two decades. Starting from an initial set of 3,309 publications obtained from academic literature search engines, we selected and analyzed 71 papers comprising 67 distinct studies. We systematically compare existing AEG and ASTG approaches with respect to (i) the targeted software and vulnerability types, (ii) the generated artifacts, (iii) the underlying generation techniques and tools employed, (iv) the required inputs, (v) the evaluation methodologies, and (vi) implementation and tool availability.
Transcript
Introduction to the show: ident: Security Radio. Generated commentary on the latest security and cryptography papers.
Nadia: We're looking at the paper: "Automated Exploit and Security Test Generation".
Elias: Here's the gist of the paper. A Systematic Literature Review on Automated Exploit and Security Test Generation surveys existing techniques for automatically generating exploits and security tests for software vulnerabilities to aid researchers and practitioners in understanding their characteristics and usability.
Nadia: The exploit or the Proof of Concept of the vulnerability plays an important role in developing superior vulnerability repair techniques, as it can be used as an oracle to verify the correctness of the patches generated by the tools.
Elias: However, vulnerability exploits are often unavailable and require time and expert knowledge to craft.
Nadia: Obtaining them from exploit generation techniques can be another potential solution.
Title and authors: Nadia: So we're looking at this paper called "Automated Exploit and Security Test Generation: A Systematic Literature Review." It’s by Quan-Cuong Bui, Emanuele Iannone, Maria Camporese, Jorge Hinrichs, Catherine Tony, László Tóth, Fabio Palomba, Peter Hegedűs.
Elias: Yeah I’ve seen the title. It sounds like a big survey of how people are trying to automatically create exploits and security tests for software flaws. It’s basically mapping out what’s already been done in that area over time.
Nadia: Exactly, it’s surveying existing techniques to help researchers and practitioners figure out how these things work in practice and what they can actually be used for when you're trying to fix bugs or test defenses.
Priya: So, it’s a literature review aimed at understanding the characteristics and usability of automated exploit generation techniques. That sounds useful for knowing where the current efforts are strongest or weakest.
Elias: Right, it sets up this framework by grouping all these different methods into four main categories: automated exploit generation, security testing, fuzzing, and other techniques. It’s trying to organize a lot of scattered research into something coherent.
Nadia: And it focuses mainly on memory-based vulnerabilities in C/C++ programs and web-based injection issues in PHP and Java applications. That gives us a clear scope for what they are focusing on right now.
The paper's summary: Nadia: The main point of this paper is that the exploit or the proof of concept for a vulnerability is really important because it acts like an oracle, something you can use to check if your new patch actually fixed the problem.
Elias: But those exploits are often hard to find and take a lot of expert time to craft, so getting them from automated generation techniques is seen as another way forward.
Nadia: So the goal of this survey is to help researchers and practitioners understand these existing exploit generation techniques by analyzing their characteristics and how usable they are in real-world scenarios.
Priya: It seems like they’re trying to make sense of a lot of messy research into a usable understanding for the security community. That’s important because it helps us know what tools actually exist and what's practical versus just theoretical.
Elias: They found that most of the studies they reviewed were published between two thousand eleven and two thousand twenty-three which tells you the research landscape is quite recent <ref:2502.04953#pg1>. The techniques are grouped into AEG, security testing, fuzzing, and others.
Nadia: Within automated exploit generation they highlighted control-flow hijacking as the dominant technique in their selection of studies. That’s a big focus area for them right now.
The paper's improvements: Elias: They look at how to improve this field, and they suggest ways to make things more automated. For instance, they point out that automated exploit generation can be improved by creating a workflow that ties vulnerability identification directly with exploit synthesis to generate working exploits for known flaws in a more automatic way.
Nadia: That makes sense. They suggest using techniques like symbolic execution and genetic algorithms to synthesize what they call a confident "exploit" or proof of concept for vulnerabilities. That would automate the crafting process beyond just simple input generation.
Priya: I wonder if that means we move closer to systems that can generate actual working code snippets, not just test cases, which is a big step toward practical exploitation.
Elias: They also suggest enhancing security testing systems by incorporating a wider range of tests, perhaps combining model-based testing with learning-based testing to boost coverage. This would allow the system to create more robust security test cases by using methods listed in Table six <ref:2502.04953#pg1>.
Nadia: That sounds like they want to move beyond just one method and build a more comprehensive testing suite that covers different types of potential weaknesses.
Priya: And they also suggest developing standardized metrics for assessing automation levels, things like FA, SA, and Inter, so practitioners could better understand the degree of automation in these techniques. That would help with usability assessment too.
Elias: They also address the availability issue by suggesting a mechanism to automatically check if proposed tools are public or licensed. This directly tackles whether these techniques are actually usable right now without requiring human intervention for every single step.
Conclusion: Nadia: So, to wrap up this review of "Automated Exploit and Security Test Generation: A Systematic Literature Review," the authors found sixty-six relevant research papers introducing or improving techniques for automatically generating exploits or security tests for software vulnerabilities.
Elias: It’s a big collection of work, and it shows that automated methods are definitely gaining traction in this space over the last decade. But they also noted that more than eighty percent of the selected studies claimed their tools could be fully automated without any human intervention.
Priya: That eighty percent is interesting, but we have to remember what those claims actually mean in practice, right? We need to see if that automation holds up when you try to use it on a real target system.
Nadia: They also pointed out that most proposed techniques still lack available tools because of security concerns, which is a big hurdle for adoption. This survey helps researchers understand the current limitations of these practices and where the gaps are right now.
Elias: The authors plan to define a clear workflow for developing these automated exploit generation tools in their future work, which gives us a direction for what comes next in this research area.
Priya: It’s good to have that roadmap so we know what to look out for when the next wave of tools comes out. It’s about seeing if the theoretical improvements translate into something you can actually run on your machine.
Nadia: So, that's our take on this paper, "Automated Exploit and Security Test Generation: A Systematic Literature Review." It gives us a solid map of the automated exploit generation landscape as we move forward.
More episodes
- 2608.27496-ROPE: Routed Origin Policy Enforcement against Indirect Prompt Injection
- Daily Summary for 2026-11-19
- 2607.07085-Is Randomness Necessary for Adaptive Data Analysis?
- The day in conversation for 2026-11-19
- Daily Summary for 2026-11-19
- 2609.10601-Threshold Choice, Not Sample Size, Bounds Trustless Verification of Nondeterministic Compound AI Workflows
- 2610.38786-Adversarial Process Disturbances at a Deployable Alarm Budget: Detector Evaluation on a Simulator and a Real Plant
- 2511.08660-Binary and Multiclass Cyberattack Classification on GeNIS Dataset
- 2604.27302-Static Attribution of Android Residential Proxy Malware Using Graph Kernels
- Daily Summary for 2026-11-18