Can We Generate Shellcodes via Natural Language? An Empirical Study

Writing software exploits is an important practice for offensive security analysts to investigate and prevent attacks. In particular, shellcodes are especially time-consuming and a technical challenge, as they are written in assembly language. In this work, we address the task of automatically generating shellcodes, starting purely from descriptions in natural language, by proposing an approach based on Neural Machine Translation (NMT). We then present an empirical study using a novel dataset (Shellcode_IA32), which consists of 3,200 assembly code snippets of real Linux/x86 shellcodes from public databases, annotated using natural language. Moreover, we propose novel metrics to evaluate the accuracy of NMT at generating shellcodes. The empirical analysis shows that NMT can generate assembly code snippets from the natural language with high accuracy and that in many cases can generate entire shellcodes with no errors.

. For example, in June 2021, GitHub updated its policy on malware and exploit research by allowing and even encouraging users to post proof-of-concept (PoC) exploits or vulnerabilities on the platform [64].
Among software exploits, code-injection attacks are considered the most dangerous ones, since they have the worst consequences on the victim organizations [61]. Moreover, code-injection attacks have been drastically increasing with the growth of applications exposed to the Internet [75], as shown by statistics from the Common Vulnerabilities and Exposures (CVE) database [16]. These attacks deliver and run malicious code (payload) on the victims' machine, in order to give attackers control of the target system. Since the payload is typically designed to launch a command shell, the hacking community generically refers to the payload portion of a code-injection attack as a shellcode. Other objectives of shellcodes include killing or restarting other processes, causing a denial-of-service (e.g., a fork bomb), leaking secret data, etc. Listing 1 shows an example of shellcode 1 in assembly for Linux OS running on the 32-bit Intel Architecture).
The development of software exploits is a technically difficult activity. Shellcodes are typically written in assembly language, in order to gain full control on the layout of code and data in stack and heap memory, to make the shellcode more compact, to obfuscate the code, and to perform low-level operations on data representation [18,29,3,63]. However, programming in assembly is time-consuming and has low productivity compared to high-level languages [17,43,72].
In order to make assembly programming easier and more efficient, we investigate the use of Neural Machine Translation (NMT) for the generation of shellcodes. In general, NMT translates between different languages (including natural and programming languages), using Natural Language Processing (NLP) and Deep Learning (DL) techniques [31,7,83,9], in order to learn the typical idioms of a target programming language from datasets of annotated programs. NMT is an emerging approach for code generation [88,56] and other programming tasks, such as code completion [23,77], the generation of UNIX commands [52,53] or commit messages [44,58,45], etc. However, NMT techniques have not heretofore been applied in the field of software security to generate software exploits. In our case, developers would translate a description (intent) of a piece of code in English, into the corresponding code snippet in assembly language. For example, developers can use NMT to generate code snippets that they could not recall, or that are not yet confident to write themselves, similarly to querying a search engine, with the additional benefit of tailoring the code according to their query.
In this paper, we introduce a novel approach for generating shellcodes in assembly language, from their description in natural language. Differing from previous research, which adopts static and/or dynamic program analysis (e.g., fuzzing, program synthesis, etc.), we adopt a novel statistical, data-driven approach. Specifically, our approach leverages state-of-the-art NMT techniques. Since NMT has never been applied to low-level languages such as assembly, our approach extends NMT by introducing an Intent Parser specialized for the assembly language and adopts transfer learning to bootstrap an NMT model from a training set of shellcodes. Then, the pa-Listing 1: Assembly code used to generate a shellcode on Linux OS running on 32 bit Intel Architecture. Lines 5-6, 11-12, 15-16, 19-20, 21-22-23, 24-25, 27-28-29 are multi-line snippets generated by seven different intents.
per presents an extensive evaluation of the NMT approach. As there is no unique metric able to comprehensively represent the quality of translations, we introduce new metrics for this purpose. Indeed, the generated assembly code can have high accuracy compared to the ground truth, yet it may not be a working shellcode. Or, the generated program can be compilable and executable, but it may not implement the intended shellcode. Or again, the generated program does not exactly match the ground truth, but it can still be a correct shellcode (e.g., by using alternate valid labels or addressing modes), and so on. Therefore, we evaluate NMT from several points of view.
In summary, this work provides the following key contributions: -We propose a novel approach for translating natural language into shellcode in assembly language, based on NMT. The approach improves the state-of-the-art by using a novel, specialized Intent Parser and transfer learning. To the best of our knowledge, this is the first effort towards applying NMT to automatically generate code for security purposes; -We release a curated, substantive corpus of real shellcodes from public databases, in order to support the training and evaluation of NMT systems for shellcode generation; -We propose novel metrics to evaluate the performance of NMT systems for shellcode generation. Different from the metrics commonly used in other code generation tasks, the metrics proposed in this work go beyond evaluating performance on single-line snippets of code and also encompass the ability to generate entire, compilable shellcodes. Moreover, we look at the semantic correctness of the generated shellcode; -We present an extensive empirical analysis of NMT techniques at generating shellcodes, supported by the proposed metrics and dataset. In the following, Section 2 discusses related work; Section 3 introduces background concepts; Section 4 presents the proposed approach; Section 5 describes the dataset; Sections 6 experimentally evaluates the approach; Section 7 describes the ethical considerations; Section 8 discusses the threats to validity of the work; Section 9 concludes the paper.

Related Work
Our work is situated at the intersection of machine translation and code/exploit generation, by applying NLP techniques to software security. Accordingly, we review related work in these areas. Neural Machine Translation for Code Generation There are several recent works that focus on generating code from natural language [91,21,74]. Ling et al. [56] and Yin and Neubig [88] proposed a novel neural architecture for code generation, while Xu et al. [84] incorporated pre-training and fine-tuning of a model to generate Python snippets from natural language using the CoNaLa dataset [87]. Furthermore, Gemmell et al. [30] used a transformer architecture with relevance feedback for code generation, and reported improvements over state-of-the-art on several datasets. There also exist approaches that perform the reverse task, i.e., generating natural language from code. Oda et al. [67] pioneered the task of translating python code to pseudo-code while others proposed an n-gram language model to generate comments from source code [65]. Iyer et al. [42] proposed an attention model that summarizes code. Code2Seq [2] embeds abstract syntax tree paths to encode context and was used for code documentation generation (generating natural language from code) and code summarization. A notable example of applying code documentation generation in software engineering is generating git commit messages from git-tracked codebase changes [44]. NMT has been widely adopted also for different programming tasks. For example, Lin et al. [53] presented new data and semantic parsing methods to address the problem of mapping English sentences to bash commands, and Zhong et al. [93] generated SQL queries from natural language. Tufano et al. [80] investigated the ability of the NMT to learn how to automatically apply code changes implemented by developers during pull requests. The authors trained the model on a dataset containing pairs of code components before and after the implementation of the changes provided in the pull requests and showed that the NMT can accurately replicate the changes implemented by developers. Hata et al. [36] presented Ratchet, an NMT-based technique that generates a fixed code for a given bug-prone code query. The technique uses a Seq2Seq model trained on pre-correction and post-correction code in past fixes. To prove the feasibility of the approach, the authors performed an empirical study on five open source projects, showing that Ratchet can generate syntactically valid statements with high accuracy.
Our empirical analysis investigates these recent advances in NMT in the context of the open problem of generating shellcodes in assembly language, from natural language intents.
Automated Exploit Generation. The task of exploit generation via automatic techniques has been addressed in several ways. ShellSwap [8] is a system that generates new exploits based on existing ones, by modifying the original shellcode with arbitrary replacement shellcode. Hu et al. [39] developed a novel approach to construct data-oriented exploits through data flow stitching, by composing the benign data flows in an application via a memory error. They built a prototype attack generation tool that operates directly on Windows and Linux x86 binaries. Avgerinos et al. [5] developed an end-to-end system for automatic exploit generation (AEG) on real programs by exploring execution paths. Given the potentially buggy program in source form, their proposal automatically looks for bugs, determines whether the bug is exploitable, and produces a working control-flow hijack exploit string. SemFuzz [92] extracts necessary information from non-code text related to a vulnerability, using natural language processing and a semantics-based fuzzing process, in order to discover and trigger deep bugs. Chen et al. [13] presented techniques to find out the gadgets, i.e., the basic building block in Jump Oriented Programming (JOP), and showed these gadgets are Turing complete. They implemented an automatic tool able to generate JOP shellcodes. Ding et al. [20] proposed a reverse derivation of a transformation method driven by state machines indicating the status of data flows, in order to transform the original shellcode into printable Return Oriented Programming (ROP) payload. Chainsaw [1] is a tool for analyzing web applications and generating injection exploits. The tool performs static analysis and defines a model of the application behavior to generate injection exploits, by leveraging application workflow structures and database schemes. Brumley et al. [11] proposed an approach for Automatic Patch-based Exploit Generation (APEG). Starting from a program and its patched version, the approach identifies the security checks added by the patch and automatically generates inputs to fail the checks. Huang et al. [40] introduced a method to automatically generate exploits based on software crash analysis. This method analyzes software crashes using a symbolic failure model, to generate exploits from crash inputs and existing exploits for several types of applications. Xu et al. [86] developed a tool to find buffer overflow vulnerabilities in binary programs and automatically generate exploits using a constraint solver. Vulnerability detection is achieved through symbolic execution and the exploit generated by this tool can bypass different types of protection.
Similar to our previous work [51], our approach uses natural language statements to generate exploits and adopts neither a static nor dynamic program analysis approach (e.g., fuzzing, program synthesis, etc.), but a statistical, data-driven approach.

Background
This section introduces background concepts on neural machine translation (NMT). We follow the notation defined by Eisenstein [26].
Machine translation refers to the translation of a language into another by the means of a computerized system [22]. It is defined as an optimization problem, which maximizes the conditional probability that a sentence ω (t) in the target language is the likely translation of a sentence ω (s) in the source language, by using a scoring function ψ: The resolution of the problem requires a decoding algorithm for computingω (t) , and a learning algorithm for estimating the parameters of the scoring function ψ. Neural network models for machine translation are based on the encoder-decoder architecture [14]. The encoder network converts the source language sentence into a context vector or matrix representation z of fixed length. The decoder network then converts the encoding into a sentence in the target language by defining the conditional probability p(ω (t) |ω (s) ).
The decoder is typically a recurrent neural network, which generates the target language sentence one word at a time, while recurrently updating a hidden state. The encoder and decoder networks are trained end-to-end from parallel sentences. If the output layer of the decoder is a logistic function, then the entire architecture can be trained to maximize the conditional log-likelihood: where the hidden state h (t) m−1 is a recurrent function of the previously generated text ω (t) 1:m−1 and the encoding z, while β ∈ R (V (t)×K ) is the matrix of output word vectors for the V (t) words in the target language vocabulary, and K is the dimension of the hidden state. Seq2Seq. The simplest encoder-decoder architecture is the sequence-to-sequence model [78]. In this model, the encoder is set to the final hidden state of a long short-term memory (LSTM) [38] on the source sentence: where x (s) m is the embedding 2 of the target language word ω (s) m . The encoding then provides the initial hidden state for the decoder LSTM: where m is the embedding of the target language word ω (t) m . Sequence-to-Sequence translation is nothing more than wiring together two LSTMs: one to read the source, and another to generate the target. Attention Mechanism. The weakness of using a fixed-length context vector is the difficulty to remember long sentences. Indeed, in the traditional Seq2Seq model, the intermediate states of the encoder are discarded, and only the final states (vector) are used to initialize the decoder. To overcome this limitation, Bahdanau et al. [7] proposed the attention mechanism, i.e., a solution that uses a context vector to align the source sentence and target sentence. The context vector holds the information from all hidden states from the encoder and aligns them with the current target output. By using this mechanism, the model is able to look at a specific part of the source sentence and better understand the relationship between the source and target. An attention function can be described as mapping a query and a set of key-value pairs to an output, where the query, keys, values, and output are all vectors. The keyvalue-query concepts come from retrieval systems. For example, when a user types a query to search for a resource (value) on a contents-sharing platform, the search engine maps the query against a set of keys associated with the resources in the database of the platform and will show to the user the best-matched resource. Formally speaking, for each key n, the attention mechanism assigns a score σ a (m, n) with respect to the query m, based on how much they match. In Bahdanau's paper, the score is parametrized by a feed-forward network with a single hidden layer. The output of this activation function is a vector of non-negative numbers [α m→1 , α m→2 , . . . , α m→N ] T , with length N equal to the size of the memory (i.e., the space of all the generated words). Each value in the memory v n is multiplied by the attention α m→n ; the sum of these scaled values is the output. At each step m in decoding, the attentional state is computed by executing a query, which is equal to the state of the decoder, h (t) m . The resulting compatibility scores are: Transformer. In the encoder-decoder model, the keys and values used in the attention mechanism are the hidden state representations in the encoder network z, and the queries are state representations in the decoder network h (t) . Vaswani et al. [82] proposed a new model architecture, the Transformer, that does not rely on the recurrent neural networks by applying self-attention [54,46]) within the encoder and decoder. For level i, the basic equations of the encoder side of the transformer are: For each token m at level i, we compute self-attention over the entire source sentence. The keys, values, and queries are all projections of the vector h (i−1) . The attention scores α (i) m→n are computed using a scaled form of softmax attention. This encourages the attention to be more evenly dispersed across the input. Self-attention is applied across multiple "heads", each using different projections of h (i−1) to form the keys, values, and queries. The output of the self-attentional layer is the representation z (i) m , which is then passed through a two-layer feed-forward network, yielding the input to the next layer h (i) .
The Transformer architecture first refines the input embedding of each token, by combining it with a positional encoding vector. The architecture has a different positional encoding vector for each position of the sentence, in order to enrich the input embedding with positional information. Then, the transformed input embeddings sequentially go through the stacked encoder layers, which all apply a self-attention process. The self-attention further refines an input embedding, by combining it with the other input embeddings for the sentence in a weighted way, in order to account for correlations among the words (e.g., to get information for a pronoun from the noun it refers to, the input embedding of the noun is given a large weight).
For more detailed information on NMT models, we refer the reader to the work of Eisenstein [26].

Approach
We leverage neural machine translation (NMT) to automatically generate shellcodes starting from their natural language description. Following prior work (e.g., [60]), we build a neural network that directly models the conditional probability of translating an intent, in natural language into a code snippet in assembly language.
The main challenge towards the goal of automatically generating shellcodes is represented by the programming language, i.e., the assembly. This language is significantly different from other languages addressed so far by research on NMT, which focused so far on mainstream imperative languages such as Python and Java. Assembly is a low-level programming language with many syntactical differences from these languages. For example, assembly does not provide the concept of variable, which is instead replaced by registers, memory addresses, addressing modes, and labels. Moreover, some programming constructs in assembly require multiple statements, which instead could be expressed with only one statement of other programming languages. To address this new language for NMT, we opted to base our solution on existing deep neural network architectures: Seq2Seq with Attention, and CodeBERT. We refrained from proposing a new architecture, for several reasons: (i) using an existing, well-tested architecture can be used with more confidence in a comparative setting in which numerical issues (such as, the vanishing gradient) can be prevented; (ii) existing architectures were shown to perform well when translating from English descriptions, which is also the case of our problem; (iii) using an existing architecture enables us to reuse pre-trained models, which are costly to pre-train from scratch in terms of data size, computational time, and resources. Furthermore, assembly is a low-resource programming language and its codebases are scarce data compared to mainstream program languages and, therefore, it would be a challenge to pre-train a model from scratch on assembly-based shellcode bases. Since NMT for assembly code-based shellcodes is not investigated in prior works, there are limited resources for processing assembly codebases such as abstract syntax trees (AST), which are abundant for other programming languages and provide domain knowledge for some existing code generation architectures. Due to these reasons, we hence wanted to thoroughly investigate the strengths and weaknesses of current architectures. In the following, we briefly describe these architectures.
Seq2Seq is a common model used in a variety of neural machine translation tasks. Similar to the encoder-decoder architecture with Bahdanau's attention mechanism [7], we use a bi-directional LSTM as the encoder, to transform an embedded intent sequence into a vector of hidden states with equal length. Within the bidirectional LSTM encoder, each hidden state corresponds to an embedded token. The encoder LSTM is bidirectional, which means it reads the source sequence ordered from left to right and from right to left. To combine both directions, each hidden state for the bidirectional LSTM encoder is computed by concatenating the forward and backward hidden states in the encoder.
CodeBERT [28] is a large multi-layer bidirectional Transformer architecture [82]. Like Seq2Seq, the Transformer architecture is made up of encoders and decoders. CodeBERT has 12 stacked encoders and 6 stacked decoders. Compared to Seq2Seq, the Transformer architecture introduces mechanisms to address key issues in machine translation: (i) the translation of a word depends on its position within the sentence; (ii) in the target language, the order of the words (e.g., adjectives before a noun) can be different from the order of words in the source language (e.g., adjectives after a noun); (iii) several words in the same sentence can be correlated (e.g., pronouns). These problems are especially important when dealing with long sentences. Different from Seq2Seq, CodeBERT also comes with a pre-trained neural network model, learned from large amounts of code snippets and their descriptions in the English language, and covering six different programming languages, including Python, Java, Javascript, Go, PHP, and Ruby. The goal of pre-training is to bootstrap the training process, by establishing an initial version of the neural network, to be further trained for the specific task of interest [70,57,19,10]. This approach is called transfer learning. In our case, we train the CodeBERT model to translate English intents to assembly code snippets using our dataset (see § 5).
To better support such existing models at performing a new translation task, we extended the process with data processing. Data processing is an essential step to sup-  port the NMT models in the automatic code generation and refers to all the operations performed on the data used to train, validate and test the models. These operations strongly depend on the specific source and target languages to translate (in our case, English and assembly language). We process data through a pipeline of steps, which we tailored for the task of generating assembly code snippets. The data processing steps are performed both before translation (pre-processing), to train the NMT model and prepare the input data, and after translation (post-processing), to improve the quality and the readability of the code in output. Figure 1 shows the architecture of our approach, along with an example of inputs and outputs at each step, further discussed in the following.

Pre-Processing
The pre-processing starts with the stopwords filtering, i.e., by removing a set of custom compiled words (e.g., the, each, onto), in order to include only relevant data for machine translation. This phase also includes the identification of tokens, i.e., basic units which need not be decomposed in subsequent processing. Therefore, the input sequences of natural language tokens and assembly code are split in a process called tokenization. The tokenizer converts the input strings into their byte representations, and learns to break down a word into subword tokens (e.g., lower becomes [low,er]. We tokenize intents using the nltk word tokenizer [59] and snippets using the Python tokenize package [73]. One task for code generation systems is to prevent non-English tokens (e.g., start) from getting transformed during the learning process. This process is known as object standardization. Abstracting important words for the assembly language can make it easier for the model to reuse existing structures learned from other imperative languages, such as moving data and changing the control flow. To perform the standardization, we adopt an intent parser, which takes in input a natural language intents and provides as output a dictionary of standardizable tokens (i.e., it identifies the correct names for the standardization process), such as the names of the registers, the actions (e.g., /bin/sh), the hexadecimal values, etc. We implement the intent parser using spaCy, an open-source, industrial-strength Natural Language Processing library written in Python and Cython. We also use custom rules defined with regular expressions to identify hexadecimal values (e.g., 0xbb), strings that fall between quotation marks, squared brackets, variable name notations (e.g., variableName, variable name), function and register names, mathematical expressions, and byte arrays (e.g., \xe3 \xa1). Hence, this component is tailored for the task of generating shellcodes in assembly language starting from their natural language description.
All tokens selected by the parser are therefore passed to the Standardizer. The standardization process simply replaces the selected token in both the intent and snippet with var#, with # denoting a number from 0 to |l|, and |l| is the number of tokens to standardize. In Fig. 1, the intent parser identifies 0xf2, and start as standardizable tokens and standardizes them to var0, and var1 respectively (based on order of appearance in the intent). To improve the process, we prevent the standardization of unimportant tokens, by compiling a dictionary of 45 assembly keywords (e.g., register, address, byte, etc.) as non-standardizable tokens. After the standardization process, both the original token and its standardized counterpart (var#) are stored in a dictionary (named Slotmap) to be used during post-processing to restore the original words.
Lastly, we create word embeddings, i.e., we map each token (in both the intent and code snippet sequences) into a numerical id representation in order to capture their semantic and syntactic information, where the semantic information correlates with the meaning of the tokens, while the syntactic one refers to their structural roles [49].

Post-Processing
Post-processing is an automatic post-editing process, applied during decoding in the translation process (i.e., after the generation of the code snippet). This phase include a Destandardizer, which uses the slot map dictionary generated by the parser to replace all keys in the standardized intent (i.e., var0 and var1) with the corresponding memorized values (i.e., 0xf2, and start).
The generated snippets are then further post-processed using regular expressions. This operation includes the removal of (any) extra-spaces in the output (e.g., between operations and operands), and the removal of (any) extra-backslashes in escaped characters (e.g., \\n). Also, during the post-processing, newline characters \n are replaced with new lines to generate multi-line snippets. As a final step, snippet tokens are joined to form a complete code snippet.

Dataset
We curated and released a dataset for, Shellcode IA32 [50], specific to shellcode generation. This dataset consists of 3, 200 examples of instructions in assembly language for IA-32 (the 32-bit version of the x86 Intel Architecture) collected from publicly available security exploits. The x86 is a complex instruction set computer (CISC), in which single instructions can perform several low-level operations (such as a load from memory, an arithmetic operation, and a memory store) or are capable of multistep operations or addressing modes within single instructions. The dataset is comparable in size to the popular CoNaLa dataset [89] (2, 379 training and 500 test samples in the annotated version of the dataset), which is the basis for state-of-the-art studies in NMT for Python code generation [87,91,30].
We collected assembly programs used to generate shellcode from shell-storm [76] and from Exploit Database [27], in the period between August 2000 and July 2020. We focus on shellcode for Linux, the most common OS for security-critical network services. Accordingly, we gathered assembly instructions written for the Netwide Assembler (NASM) for Linux [24]. NASM is a line-based assembler. Figure 2 shows a simple example of a NASM source line. Every source line contains a combination of four fields: an optional label, to symbolically represent the address of an opcode or data location defined by the line; a mnemonic or instruction, which identifies the purpose of the statement and is optionally followed by operands specifying the data to be manipulated; an optional comment, i.e., free text ignored by the compiler. A mnemonic is not required if a line contains only a label or a comment. The assembly programs collected in the dataset implement a varied set of shellcode attacks. One of the most common and basic shellcodes is the execution of a system shell (e.g., the /bin/sh command). This shellcode is often used in combination with more sophisticated attacks. The main categories include: exfiltrating password, e.g., from /etc/passwd (a plain text-based database that contains information for all user accounts on the system); breaking a chroot jail (an additional layer of security to run untrusted programs, which can be evaded by invoking vulnerable system calls with malicious inputs); running executables with the file system permissions of the executable's owner; flushing firewall rules (e.g., IPtables). Another form of shellcodes is the egg hunter, i.e., a piece of code that when executed looks for other pieces of code (usually bigger) called the egg and passes the execution to the egg. This technique is usually used when the space of executing shellcode is limited (the available space is less than the egg size) and it is possible to inject the egg into another memory location. Shellcodes are also used to perform denial-of-service (DoS) attacks, such as for the fork-bomb attack, in which a process continually replicates itself to deplete system resources, slowing down or crashing the system due to resource exhaustion. Among the most complex shellcodes, we find the bind shell attacks. These attacks, which can easily reach hundreds of bytes, are used to open up a port on the victim system and connect to it from the remote attacking box. The complexity further increases when an attack redirects all inputs and outputs to a socket (reverse shell) in order to evade firewalls.
Each sample of the Shellcode IA32 dataset represents a snippet -intent pair. The snippet is a line or a combination of multiple lines of assembly code, following the NASM syntax. The intent is a comment in the English language (c.f. Listing 1). To take into account the variability of descriptions in natural language, multiple authors described independently different samples of the dataset in the English language. Where available, we used as natural language descriptions the comments written by developers of the collected programs. Moreover, in the preliminary phase of the dataset collection, we enriched the dataset with lines of assembly code and their relative English comments extracted from popular tutorials and books [25,48,81]. This helped us to learn the typical style for describing assembly code and to mitigate bias in our descriptions in English of assembly code. Once we reached confidence about the description style (i.e., the description style was recurring when adding more samples), we focused our efforts on real shellcodes, by writing ourselves the descriptions where no comment or documentation about the code snippet was available. Our dataset consists of 10% of instructions collected from books and guidelines, while the rest are from real shellcodes. However, there is no qualitative difference between both sets.
Multi-line Snippets: Since assembly is a low-level language, it is often necessary to use multiple instructions to perform a given task. Thus, we go beyond one-to-one mappings between a line of code and its comment/intent. For example, a common operation in shellcodes is to save the ASCII string "/bin/sh" into a register. This operation requires three distinct assembly instructions: push the hexadecimal values of the words "/bin" and "//sh" onto the stack register before moving the contents of the stack register into the destination register (lines 27-28-29 in Listing 1). It would be meaningless to consider these three instructions as separate. To address such situations, we include 510 lines (∼ 16% of the dataset) of intents that generate multiple lines of shellcodes (separated by the newline character \n). Table 1 shows two further examples of multi-line snippets with their natural language intent.
Statistics: Table 2 presents descriptive statistics of the Shellcode IA32 dataset. The dataset contains 52 distinct assembly mnemonics, excluding declarations of functions, sections, and labels. The two most frequent assembly instructions are mov (∼ 30% frequency), used to move data into/from registers/memory or to invoke a system call, and push (∼ 22% frequency), which is used to push a value onto the stack. The next most frequent instructions are the cmp (∼ 7% frequency), xor and jmp instructions (∼ 4% frequency). The low-frequency words (i.e., the words that appear only once or twice in the dataset) contribute to the 3.6% and 7.3% of the natural language and the assembly language, respectively. Fig. 3 shows the distribution of the number of tokens across the intents and snippets in the dataset. We publicly shared our entire Shellcode IA32 dataset on a GitHub repository. 3

Experimental Analysis
This section presents an extensive evaluation of our approach to generating shellcodes from natural language descriptions. We conducted the experimental analysis to target the following experimental objectives. £ Feasibility in applying NMT for shellcode generation.
We first perform an initial assessment on the feasibility of using NMT for shellcode generation with reasonably good accuracy, by applying techniques commonly used for code generation (e.g., generating Python code from natural language). We evaluate a broad set of state-of-the-art models for code generation, in combination with different techniques for data processing. In this initial stage, we adopt automatic evaluation metrics. £ Accuracy of NMT at generating assembly code snippets.
In this experimental objective, we deepen the analysis of the accuracy of NMT models. This is a cumbersome task since automatic metrics do not catch the deeper linguistic features of generated code, such as its semantic correctness [34]. Therefore, it is also advisable for NMT studies to perform an evaluation through manual analysis, by using additional metrics in order to have a more precise and complete evaluation. The second experimental objective still focuses on the analysis of individual intents and their corresponding translations into code snippets. £ Accuracy of the NMT at generating whole shellcodes. We investigate if it is possible to apply NMT to generate full shellcodes, i.e., entire assembly programs from a set of intents. Ideally, the generated code is entirely or mostly correct, in order to reduce the human effort towards developing assembly programs. Therefore, in this experimental objective, we evaluate how many entire shellcodes are correctly generated by NMT (unlike the previous experimental objective, where we analyze individual code snippets regardless of which program they belong to). £ Types of errors incurred by NMT in the generation of shellcodes.
In this experimental objective, we are concerned with diagnosing the error predictions in the code generation task. We qualitatively analyze a representative sample of the most frequent mistakes, including both syntactic and semantic ones, to get more insight into the severity of the errors, and to understand potential areas of improvement for future work.
Our CodeBERT implementation uses an encoder-decoder framework where the encoder is initialized to the pre-trained CodeBERT weights, and the decoder is a transformer decoder. The decoder is composed of 6 stacked layers. The encoder fol-lows the RoBERTa architecture [57], with 12 attention heads, hidden layer dimension of 768, 12 encoder layers, 514 for the size of position embeddings. We use the Adam optimizer [47]. The total number of parameters is 125M. The max length of the input is 256 and the max length of inference is 128. The learning rate α = 0.00005, batch size = 32, beam size = 10, and train steps = 2800.
We performed our experiments on a Linux machine. Seq2seq utilized 8 CPU cores and 8 GB RAM. CodeBERT utilized 8 CPU cores, 16 GB RAM, and 2 GTX1080Ti GPUs. The computational time needed to generate the output depends on the settings of the hyper-parameters and the size of the dataset. On average, the training time for the Seq2Seq model was ∼ 60 minutes, while CodeBERT required for the training on average ∼ 220 minutes. Once the models are trained, the time to translate intent into a code snippet is below 1 second and can be considered negligible.

Test Set
To perform the experimental evaluation, we split our entire dataset into train/dev/test sets by using an 80/10/10 ratio. To divide the data between training, dev, and test set, we did not individually sample intent-snippet pairs from the dataset, but we took groups of intent-snippet pairs that belonged to the same shellcode, in order to be able to evaluate generate shellcodes in their entirety (see § 6.5). The test set contains 30 complete shellcodes (e.g. the entire Listing 1).
We selected the 30 shellcodes of the test set in order to maximize the heterogeneity among the programs and mitigate bias. We anticipated that these biases could affect the evaluation: the type of attack (as they may entail different instructions and constructs); the authors of the shellcode (as it may also affect the programming style); and the complexity of the shellcode (as more complex shellcodes may also be more difficult to describe and to translate). We divided the shellcodes according to the type of the attack (shell spawning, break chroot, fork bomb, etc.), and sampled the shellcodes uniformly across these classes. When sampling within each class, we doublechecked that no programmer was over-represented. We used the shellcode length as a proxy for complexity, and we increased the sample size until the distribution of the shellcode length was comparable to the distribution of the whole population (min=12, max=61, mean=26.9, median=24.5). The histograms in Fig. 4 summarize the statistic of the programs in the test set in terms of lines of code. Additional information on the test set is presented in the Appendix A.

Feasibility in applying NMT for shellcode generation
We first analyze the feasibility of Seq2Seq with attention mechanism and CodeBERT for the generation of shellcodes and investigate the impact of the data processing described in § 4. In this stage, we use automatic evaluation metrics. Automatic metrics are commonly used in the field of machine translation. They are reproducible, easy to be tuned, and time-saving. The BiLingual Evaluation Understudy (BLEU) [69] score is one of the most popular automatic metric [67,56,30,79]. This metric is based on   the concept of n-gram, i.e., the adjacent sequence of n items (e.g., syllables, letters, words, etc.) from a given example of text or speech. In particular, this metric measures the degree of n-gram overlapping between the strings of words produced by the model and the human translation references at the corpus level. BLEU measures translation quality by the accuracy of translating n-grams to n-grams, for n-gram of size 1 to 4 [33]. The Exact match accuracy (ACC) is another automatic metric often used for evaluating neural machine translation [56,89,90,91]. It measures the fraction of the exact match between the output predicted by the model and the reference.
To assess the influence of our tailoring to NMT for the assembly language (e.g., the intent parser), we compare three "variants" of NMT by varying the steps of the data processing pipeline (see § 4): w/o data processing: the model performs the translation task without applying any step of the data processing pipeline. w/o intent parser: in this case, the model is trained on processed data, but without adopting the intent parser. with intent parser: the data processing pipeline also includes the intent parser. Table 3 shows the results of this analysis. The table shows that the data processing aids the Seq2Seq model also without the use of the intent parser, while CodeBERT does not take benefit from the basic data processing steps. The performance of both models significantly increases when the data processing is used in combination with the intent parser. Indeed, the full data processing pipeline improves all the metrics by ∼ 31% on average for Seq2Seq and by ∼ 19% on average for CodeBERT when the results of the models are compared without using the data processing process. The table also highlights that CodeBERT outperforms the Seq2Seq model across all metrics. We conducted a paired t-test and found that the differences between the results obtained by CodeBERT with the intent parser and all the other model configurations are statistically significant for all metrics (at p < 0.05).
To estimate the actual goodness of the results, we compared the best performance achieved on the Shellcode IA32 dataset with the state-of-the-art best performances on  [91], respectively, and are therefore lower than the best results in Table 3. We attribute these differences to the nature of the assembly language, which is a low-level language. Indeed, even if this work targets the IA-32 processor, which is a CISC architecture, the instruction set of the assembly language is still limited if compared to high-level languages, such as Python, which include a wide number of libraries and functions and, therefore, are more complex to automatically generate.
We also investigate the performance of the code generation task on single-line snippets vs. multi-line snippets by performing a fine-grained evaluation. Table 4 shows the performance of CodeBERT (with data processing) for single vs. multi-line snippets. Unsurprisingly, we find that accuracy is negatively affected by the length of snippets, while BLEU scores are higher for multi-line snippets. This is because multi-line snippets are longer, there is more opportunity for BLEU scores to be higher (there can be more n-grams that are matched in longer snippets), in contrast to single line snippets. And likewise, since the accuracy metric is an exact match on the entire snippet, performance on multi-line snippets is lower than for single line snippets. This first analysis allows us to conclude that the state-of-the-art NMT models can be applied for the generation of code used to exploit the software, and provide high performance when used in combination with data processing.
6.4 Accuracy of NMT at generating assembly code snippets In § 6.3, we used the code written by the programmers (i.e., the authors of the shellcodes) as ground truth for the evaluation. Therefore, when the model predicts the assembly code snippets starting from their natural language description, the predicted output is compared to code composing the original shellcode attacks. However, since the same English intent can be translated into different but equivalent assembly snippets, automated metrics (such as BLEU scores) are not perfect in that they do not credit semantically correct code that fails to match the reference. For example, the snippets jz label and je label are semantically identical, even if they use different instructions (jz vs. je). Furthermore, these metrics do not indicate whether the generated code would compile or not. Accordingly, we define two new metrics: a generated output snippet (single or multi-line) is considered syntactically correct if it is correctly structured in assembly language and compiles correctly. The output is considered semantically correct if the snippet is an appropriate translation in assembly language given the intent description. Consider the intent transfer the contents of the ebx register into the eax register. If the approach generates the snippet mov ebx, eax, then the snippet is considered syntactically correct (it would compile), but not semantically correct because the order of the operands is inverted. These two metrics allow us to assess the deeper linguistic features of the code [35]. The semantic correctness implies syntax correctness, while a snippet can be syntactically correct but semantically incorrect. When a snippet is syntactically incorrect it is also semantically incorrect. The evaluation of the semantic equivalence between the output predicted by the models and the code written by the authors of the shellcodes provides the best insights into the quality of the output since it allows us to assess the correctness of the predicted code even if its syntax differs from the ground truth. This is the reason why we did not limit the analysis to automatic metrics, and manually evaluated the semantic meaning of generated code.
To evaluate the syntactic correctness of the outputs, we used the NASM compiler in order to check whether the code is compilable, while we evaluated the semantic correctness by checking if the code generated by the models is a correct translation of the English intent. We performed this analysis manually, by checking every single line of generated code. This analysis could not be performed automatically, since an English intent can be translated into several forms that are different, but semantically equivalent. For the same reason, manual ("human") evaluation is a common practice in NMT studies. The manual evaluation also gives better insights into the quality of machine translation and allows us to analyze errors in the output. To reduce the possibility of errors in manual analysis, multiple authors performed this evaluation independently, obtaining a consensus for the semantic correctness of the output predicted by the models. Table 5 shows the percentage of syntactically and semantically correct snippets across all the examples of the test set. We evaluated the performance of Seq2Seq and CodeBERT, both using data processing. Both syntactic and semantic evaluations were performed by compiling the generated snippets under the NASM compiler. Table 5 shows that both approaches are able to generate > 95% of syntactically correct snippets. Paired t-tests indicated that the differences between the models are not statistically significant for the syntactic correctness, but they are statistically significant for semantic correctness (at p < 0.01). Again, we further investigated the results provided by CodeBERT, by evaluating the performance of the model on single vs. multi-line snippets. Table 6 highlights that the multi-line snippets affect model performance on syntactic correctness, although we find no statistically significant difference in model performance on the semantic correctness metric.  Table 7 show illustrative examples of code snippets that the model can successfully translate (i.e., the snippets generated by the approach are syntactically and semantically correct). Rows 3, 6, and 8 are examples of correct snippets that are penalized by automated metrics, even if they do not exactly match the ground truth. Despite some slight differences with the ground truth, the generated code is semantically correct, due to the ambiguity of the assembly language. Thus, these differences are still considered correct by our manual analysis. We note correctly generated examples of multi-line snippets in rows 2, 3, 4, and 6. Also, we observe in row 3, the ability to generate multi-line snippets from a relatively abstract intent.
We conclude that both Seq2Seq and CodeBERT provide syntactically and semantically correct code snippets with high accuracy. Moreover, CodeBERT provides the best performance in the task of generating shellcodes from natural language intents. Table 7: Illustrative examples of successfully generated snippets using our approach. Differences between the output and ground truth are bolded. Such differences are penalized by automatic metrics even though they are correct. Due to these findings, we consider CodeBERT (with data processing) as our reference NMT model for the following experimental objectives.

Accuracy of the NMT at generating whole shellcodes
The ultimate goal of developers is to craft entire shellcodes. The previous evaluation showed that NMT can generate individual code snippets that are likely the correct ones. Thus, NMT can be queried by developers to translate specific parts of a program. Here, we raise the bar for the evaluation, by analyzing to which extent NMT can generate an entire shellcode. To this purpose, we consider groups of intents from the same exploit and compare the resulting code snippets with the original shellcode. We use two new metrics to evaluate the ability of the approach to generate semantically and syntactically correct code for entire shellcodes. Let n i t be the the number of total lines of the i-th program in the test set (i ∈ [1,30]). Let also consider n i syn as the number of automatically-generated snippets for the i-th program that are syntactically correct, and n i sem as the number of automaticallygenerated snippets that are semantically correct. For every program of the test set, we define the syntactic correctness of the program i as the ratio n i syn /n i t , and the semantic correctness of the program as the ratio n i sem /n i t . To perform a conservative evaluation on multi-line snippets, even if only one line of code of the generated snippets is syntactically (semantically) incorrect, we consider all the lines belonging to the multi-line block as syntactically (semantically) incorrect. Both metrics range between 0 and 1.
For each i ∈ [1,30], we computed the values n i syn and n i sem for the assembly programs in the test set. We found that the average syntactic correctness over all the programs of the test set is ∼ 98% (standard deviation is ∼ 4%). Similarly, we estimated the average semantic correctness, which is equal to ∼ 96% (standard deviation is ∼ 6%). Out of 30 programs, we found that 21 are compilable with NASM and executable on the target system.
Since even one incorrect line of code suffices to thwart the effectiveness of a shellcode, we analyzed how many shellcodes could be generated with no errors. We consider a shellcode as fully correct if all the assembly instructions composing the shellcode are individually semantically correct (i.e., n i sem /n i t = 1). This evaluation metric is a demanding one. Even if one single line of the shellcode is not semantically correct, then the whole program is considered as not correctly generated. Despite this conservative evaluation, our approach is able to correctly generate 16 out of 30 whole shellcodes. Figure 5 shows the summary statistics with a density and a box plot, differentiating the fully correct shellcodes from the incorrect ones. As expected, the complexity of the shellcode -in terms of lines of assembly code -impacts the ability of the approach to correctly generate the whole program. However, the average (and the median) length of the shellcodes incorrectly generated by the model is affected by the three assembly programs of lengths 55, 59, and 61. If we consider these shellcodes as outliers, then the group of fully correct shellcodes and the group of the incorrectly generated shellcodes are very similar in terms of size. We interpret these results as a promising indication towards our ultimate goal of generating entire shellcode programs automatically from short natural language intents.

Types of errors incurred by NMT in the generation of shellcodes
In the last experiment objective, we performed a manual inspection of the model's mispredictions. We noticed that the failure outputs fall down in the following three failure types; -Failure Type A: translation failure in generating the correct label, instruction, operand(s), or delimiter(s).  shellcodes in the test set. The labels Fully Correct and Incorrect refer to the shellcodes that are generated by the approach as fully correct (n sem /n t = 1) and incorrect (n sem /n t < 1), respectively.. C, instead, is attributed to the intent parser failure. Indeed, even if the performance of the translation task benefits from the work of the intent parser (see § 6.3), it is not perfect and can lead to a failure prediction by wrongly identifying the variable or register names, labels, etc. Moreover, the error predictions can be further classified as syntactically incorrect and semantically incorrect. We remark that the syntactic incorrectness implies the semantic one. To better illustrate the problem, we present in Table 8 a qualitative evaluation using cherry-and lemon-picked examples of failure prediction from our test set.
The first row showcases an example of failing to model because of implicit knowledge. The intent does not mention the indirect addressing mode (specified by the bracket [] in NASM syntax). In the second row, we note that the model failed to generate the newline token properly to separate the snippets with lines. This causes a syntax issue, and since it does not compile we count it as syntactically incorrect. The third row shows an example in which a byte string is declared without defining the label, while the fourth row illustrates the model's failure to predict the right instruction (the definition of the function decoder instead of the execution of the function). Both outputs do not raise an exception when compiled, therefore they are syntactically but not semantically correct. In the fifth row, we note that the intent parser correctly identifies main push in the standardization process, but fails to recognize the cl register and misidentifies ecx instead. We also note that the model predicted a mov operation between two registers (register, esp) rather than a register and a value. The predicted register does not exist in the intent hence, the output is a var3. The sixth row shows an example with incorrect instruction and inverse operands order. The remaining examples include the intent parser failing to identify explicitly stated identifiers or letters in values sometimes in long intents such as in the case of the bh register (row 7) and occasionally in simple contexts such as in the case of Define the array of bytes encodedshellcode and initialize it to 0x32, 0x51, 0x30, 0x74, 0x69, 0x63, 0x6f, 0xe4, 0x8a, 0x54, 0xe2, 0x0c, 0x81, 0xc1, 0x69, 0x30, 0x69, 0x30, 0x6a, 0x8a, 0x51, 0xe3, 0x8a, 0xb1, 0xce encodedshellcode: db 0x32, 0x51,0x30, 0x74, 0x69, 0x63, 0x6f, 0xe4, 0x8a, 0x54, 0xe2, 0x0c, 0x81, 0xc1, 0x69, 0x30, 0x69, 0x30, 0x6a, 0x8a, 0x51, 0xe3, 0x8a, 0xb1, 0xce @ @ @ @ @ @ @ @ encodedshellcode: db 0x32, 0x51, 0x30, 0x74, 0x69, 0x63, 0x6f, 0xe4, 0x8a, 0x54, 0xe2, 0x0c, 0x81, 0xc1, 0x69, 0x30, 0x69, 0x30, 0x6a, 0x8a, 0x51, 0xe3, 0x8a, 0xb1, 0xce A, Sem Push the word 0666q onto the stack push word 0666q push word 0644o C, Sem

10
Declare the read label read: section: A, C, Syn read (row 10). The last row is considered also syntactically incorrect since it is not possible to declare a label with the section assembly directive. This goes to show when there is a mistake in the standardization step, the translation may fail to work around it even if the intent seems simple. The failure outputs also provide indications on what it can be done to increase the performance of the code generation task. Most of the errors can be easily identified by the programmers: incorrect addressing modes (first row), wrong newline character (second row), missing labels (e.g., encodedshellcode in row number 3), wrong instructions (row 4, 6), undefined variables (e.g., var3 in row 5), wrong operand orders (row number 6), etc. The syntactically incorrect predictions, i.e., the predictions that do not follow the syntax, can be identified with a compiler and can be fixed through an "intelligent" post-processing phase, which should be trained to identify and fix the failure outputs. This is part of the future work.

Discussion and Lessons Learned
The experimental analysis pointed out that NMT models can efficiently generate assembly code for real shellcodes, starting from their natural description. When used in combination with data processing, the accuracy of the code generation task is high enough to support developers in developing software exploits. Even if the size and the complexity of an English intent increase, the performance of the translation task is not negatively affected. CodeBERT achieves the best performance and further justifies its wide usage to address software engineering tasks. The model is able to generate whole software exploits with syntactic and semantic correctness greater than 95%. It is also able to generate programs that are fully correct, i.e., compilable and executable on the target system. However, the complexity of the software attacks (in terms of lines of code) reduces the accuracy of generating entire programs. The analysis also pointed out that the most common error predictions are easily identifiable and can be fixed during the post-processing process.

Ethical Considerations
Recognizing that attackers use exploit code as a weapon, it is important to specify that the goal of the proof-of-concept (POC) exploits is not to cause harm but to surface security weaknesses within the software. Identifying such security issues allows companies to patch vulnerabilities and protect themselves against attacks.
Offensive security is a sub-field of security research that tests security measures from an adversary or competitor's perspective. It can employ ethical hackers to probe a system for vulnerabilities [12,32,64]. Automatic exploit generation (AEG), an offensive security technique, is a developing area of research that aims to automate the exploit generation process and to explore and test critical vulnerabilities before they are discovered by attackers [6]. Indeed, work such as ours, which studies exploits on compromised systems can provide valuable information about the technical skills, degree of experience, and intent of the attackers. By using this information, it is possible to implement measures to detect and prevent attacks [4].

Threats to Validity
NMT models: Before the era of NMT, Statistical Machine Translation (SMT) [15] was the most popular technique for software engineering (SE) problems, it still outperforms NMT in some SE problems [71]. However, since we are interested in the specific problem of code generation, we focus on NMT that has shown superior performance on public benchmarks [9], and that it is widely recognized as the premier method for the translation of different languages [83]. Our choice of the NMT models has been influenced by their popularity and the availability of mature open-source implementations. We acknowledge that using only two state-of-the-art models can be a limitation of this work. Nevertheless, we believe that these two models are valid representatives of the NMT research area, and can provide us with a realistic evaluation of NMT for code generation. Seq2Seq has been for several years the most used model for code generation tasks, and it is still widely employed in NMT studies as a baseline model. CodeBERT has pushed the boundaries in natural language processing and represents the state-of-the-art for generating code documentation given snippets, as well as retrieving code snippets given a natural language search query across six different programming languages [41]. Moreover, it has also been applied in software engineering to perform different tasks [68].
Size of our dataset: Our dataset contains 3, 200 instances, which may seem relatively small compared to training data available for other NLP tasks. The data about shellcodes is much more difficult to obtain than other data for NMT. For example, before starting the collection of the dataset, we developed a script to collect assembly code for IA-32 from all of the repositories on GitHub (by far the source most used by empirical software engineering studies). We found that the amount of available data is very limited. The data is further restricted by the fact that we are specifically interested in security-oriented assembly codes (i.e., shellcodes). Therefore, we decided to collect all the shellcodes for Linux/IA-32 from exploit-db and shell-storm, the two public databases for shellcodes most popular among the security professionals, to achieve representativeness. We collected shellcodes written over a large period (from 2000 to 2020) from a variety of authors, in order to achieve diversity. To the best of our knowledge, the resulting dataset is the largest collection of shellcodes in assembly available to date. Despite the previous considerations, we note that our dataset is comparable in size to the popular CoNaLa dataset [89] (2, 379 training and 500 test samples in the annotated version of the dataset), which is the basis for state-of-the-art studies in NMT for Python code generation [87,91,30]. Further, Shellcode IA32 contains a higher percentage of multi-line snippets (∼ 16% vs. ∼ 4%). We also note here that existing code generation datasets do contain a larger, potentially noisy, subset of training examples (ranging in several thousand) obtained by mining the web. For example, the CoNaLa mined (as opposed to the CoNaLa annotated) dataset contains 598, 237 training examples mined directly from StackOverflow [87]. We designed the proposed approach to leverage existing pre-trained models to compensate for the need for big data, by training the model using our assembly dataset.
Code description: To build the dataset, we described in the English language the shellcodes collected from publicly available exploit databases. Therefore, the description of the assembly code derives from our considerations and knowledge. However, the building process of the Shellcode IA32 dataset is not different from other corpus built from scratch. For example, Oda et al. [67] hired an engineer to create pseudocode for the Django Web application framework and obtain the corpus. We avoided a single centralized version of the code description to take into account the variability of descriptions in natural language. Indeed, multiple authors described independently different samples of the dataset in the English language, and, where available, we kept untouched the comments written by developers of the collected programs to describe the assembly code snippets. To understand how different programmers and experts describe the assembly code for IA-32 and how to deal with the ambiguity of natural language in this specific context, we took inspiration from popular tutorials and books [25,48,81].
Translation task: As assembly code is a low-level language, it often takes a long sequence of instructions to complete an atomic function. Therefore, some translations presented in the dataset are too "literal" and cumbersome. For example, instead of writing "Define the start label", a user might just as well write " start:", similarly, the intent "Push the contents of eax onto the stack" takes longer than writing the assembly instruction "push eax". However, this is a common situation in any translation task from English to programming language. For example, the Django dataset contains numerous Python code snippets that are relatively short (e.g., "chunk buffer = BytesIO(chunk)") described with with English statements that are definitely longer than the snippets ("evaluate the function BytesIO with argument chunk, substitute it for chunk buffer."). Similarly, in the CoNaLa dataset we can find shortcode snippets (e.g., "GRAVITY = 9.8") described with longer English intents ("assign float 9.8 to variable GRAVITY"). Nevertheless, we -and other datasets-still include such verbose intents to provide richer learning of NMT models. Moreover, we mitigated this problem by adding multi-line snippets, i.e., single intents described in natural language that generate more lines of assembly codes, that are closer to the intent that developers may want to use during development.
Scope of the approach: A shellcode is a piece of assembly code written specifically for exploitation purposes. From this perspective, all shellcodes are security-related programs and, therefore, the proposed approach is tailored for generating software exploits. It is an interesting question whether the proposed approach has applications beyond security. The approach is focused on assembly programs, which is the most used language for shellcodes. Thus, the processing pipeline has been designed to handle relevant elements of the assembly language, such as keywords and register names. This approach significantly contributes to generating more accurate code compared to generic NMT techniques but narrows the scope to assembly code. As future work, we are exploring the use of NMT for other programming languages, such as Python. In principle, a programmer can use the method to generate assembly code unrelated to security applications. However, the method might be less accurate in this case, since our solution is trained with a dataset of mostly security-related assembly code snippets. To be used outside security applications, the programmer would need to adopt a training dataset with more non-security assembly code (e.g., assembly code for device drivers or microcontrollers). Moreover, it may be necessary to tweak the processing pipeline to support special keywords that are not adopted for shellcodes (e.g., linking directives for embedded software). We opted to leave such extensions out of the scope of our work, as security applications are the ones that have by far the highest demand for increasing the productivity of assembly programming.

Conclusion and Future Work
We addressed the problem of automated exploit generation using natural language processing techniques. We use Neural Machine Translation to translate natural language intents into shellcode. We built and released the first dataset of shellcodes, Shellcode IA32, containing 3, 200 pairs of code snippets and intents. The dataset also contains 510 intents that generate multiple snippets. These assembly language snippets can be combined to generate shellcodes for the Intel 32-bit Architecture. Our empirical analysis demonstrated the feasibility of using NMT for this task, using both automated and manual metrics. We also propose the use of novel metrics for the task of code generation, that we anticipate would be useful to the community.
Our work enables further studies in the area, to make NMT more and more effective. We are currently working on a new engine for the post-processing phase, in order to identify and fix the assembly lines wrongly generated by the NMT model and to further improve accuracy. We are also analyzing the impact of "noisy inputs" or "perturbation" in the natural language, since human developers may provide inaccurate or incomplete descriptions of the shellcode to be generated. For example, perturbations can be introduced by replacing words with "unseen" synonyms, or by removing redundant information. In this direction, we are investigating a solution to make NMT more robust and usable, by helping the model to derive the missing information (i.e., information not explicitly stated in the English intent) from the context of the programs. Finally, as part of future research, we aim to evaluate our approach with actual humans instructing with comments, so that the evaluation could take into account how the humans perceive the actual usefulness of developing a shellcode that achieves the desired result.
Beyond our current work on extending the proposed approach, we expect that this work can support more researchers in the field. Indeed, in the era where deep learning is evolving at a quick pace and succeeding in more and more tasks with surprising accuracy, we expect in the near future the development of new deep learning architectures, which could potentially bring benefits for the automatic generation of exploits. In this light, the proposed approach and dataset represent valid means to pave the way for a new generation of offensive security methods. This work represents a first step towards the ambitious goal of automatically generating shellcodes from natural language, provides originally-collected data, enables replication, and describes successes and challenges through rigorous evaluation. Table 9 presents detailed information on the 30 shellcodes composing the test set. In particular, the table shows the URL where the shellcode is collected, the number of assembly lines of the program, the number of multi-line snippets, and the number of snippets generated incorrectly from our approach. We consider the whole shellcode generated correctly only if the approach produces 0 incorrect snippets. Our approach generated correctly 16 out of 30 whole shellcodes. Table 9: The 30 shellcodes composing the test set. We consider a shellcode executed correctly if all the generated snippets composing the program are semantically correct. n t : number of total assembly lines of the program. Multi-line: number of multi-lines snippets in the program. n syn : number of syntactically correct lines generated by the approach. n sem : number of semantically correct lines generated by the approach. www.exploit-db.com/shellcodes/48703 33 (16) 31 29 3 www.exploit-db.com/shellcodes/47877 40 (0) 40 40 4 www.exploit-db.com/shellcodes/13716 59 (0) 58 52 5 www.exploit-db.com/shellcodes/47513 14 (0) 14 14 6 www.exploit-db.com/shellcodes/47511 24 (0) 24 24 7 www.exploit-db.com/shellcodes/47481 41 (2) 40 38 8 www.exploit-db.com/shellcodes/47396 61 (15) 61 60 9 www.exploit-db.com/shellcodes/47200 29 (2) 29 28 10 www.exploit-db.com/shellcodes/47202 29 (4) 29 29 11 www.exploit-db.com/shellcodes/47108 26 (9) 26 26 12 www.exploit-db.com/shellcodes/47068 12 (0) 12 12 13