Overview

In previous activities, you converted files using languages including binary, assembly, and C++. You have successfully completed a full conversion of legacy code, from binary to C++. In this activity, you will convert legacy binary code to C++, examine the code for security vulnerabilities, fix the identified security vulnerabilities, and report on those vulnerabilities. This is a key step toward the successful completion of Project Two, which is centered on fixing security vulnerabilities. The coding for this assignment will be performed in Codio. You will submit the completed Binary to C++ With Security Vulnerabilities Activity Template Word Document and a new binary file and CPP file.

Prompt

Specifically, you must address the following rubric criteria:

1. Convert the binary file to assembly code.
   • These files can be found in the Software Reverse Engineering Playground in the Module Six file folder in Codio.

1. Explain the functionality of the blocks of assembly code.
   • Use the Binary to C++ With Security Vulnerabilities Activity Template to complete this step.

1. Convert the assembly code to binary.
   • Create a new binary file for submission.

1. Convert the assembly code to C++ code.
   • Use the Binary to C++ With Security Vulnerabilities Activity Template to complete this step.
   • Compile the C++ code in the Eclipse integrated development environment.

1. Identify the security vulnerabilities within the C++ code.
   • Comment within the C++ code to indicate where the security vulnerabilities are identified.

1. Fix the identified security vulnerabilities within the C++ code.
   • Correct the C++ code to fix the security vulnerabilities.

1. Explain how the updated C++ code fixes the identified vulnerabilities.
   • Comment within the C++ code to indicate how the security vulnerabilities were fixed.

Guidelines for Submission

This should be a Word document. Use the Binary to C++ With Security Vulnerabilities Activity Template to convert the legacy binary file into assembly, explain the functionality of the assembly code, and convert the assembly code to C++ code.

This file includes your comments on the identified security vulnerabilities, the fixes, and the comments about how the security vulnerabilities were fixed. This file is needed to ensure that the code, identified vulnerabilities, fixes, and comments are correct.

This file is needed to run the application.