Fixing c code with vulnerabilities

The current code (attached), developed by a junior developer, has several issues and is not functioning as expected. The desired functionality of the program is to allow a user to select from several choices on a menu. After the user selects the “Exit” option from the menu, the program will populate a password with ‘1’s and then display the value of the password. The program also captures a character so the screen can stay paused for review before exiting. Below are screenshots for successful program execution.

Unfortunately, not only are there security issues, the code you were provided doesn’t work as expected. For the first part of this exercise demonstrate your C developer environment is working properly. You can do this by running any of the sample C code applications. 

Modify the C code in this example to make the desired functionality work properly. Demonstrate the code works properly through screen captures and describing what changes were made to fix the functionality issues.

Carefully, review the code and perform analysis as needed. Consider the following rules and recommendations and hints for items that you might want to review. 

Note, that some rules and recommendations listed below may not be found as issues in the code. 

 STR31-C. Guarantee that storage for strings has sufficient space for character data and the null terminator. 

 MSC24-C. Do not use deprecated or obsolescent functions. 

 FIO34-C. Distinguish between characters read from a file and EOF or WEOF. 

 MSC17-C. Finish every set of statements associated with a case label with a break statement.  MSC33-C. Do not pass invalid data to the asctime() function. 

 MSC17-C. Finish every set of statements associated with a case label with a break statement. 

 DCL20-C. Explicitly specify void when a function accepts no arguments. 

 MEM30-C. Do not access freed memory. 

You can use any C compiler you have access to.