Starting from:

$50

SDEV325-Homework 3 Demonstrating Risky Resource Management Solved

In this homework you use AWS Cloud 9 to create two different unique and complete demonstrations of Risky Resource Management such as Buffer Copy without Checking Size of Input, Improper Limitation of a Pathname to a Restricted Directory, Download of Code Without Integrity Check, Inclusion of Functionality from Untrusted Control Sphere, Use of Potentially Dangerous Function, Incorrect Calculation of Buffer Size, Uncontrolled Format String, and Integer Overflow or Wraparound.  

You will provide unique code that contains the vulnerability and then provide an updated version of the code that fixes the vulnerability. You should also describe why the original code was vulnerable and discuss specific attack methods a user could try to exploit the vulnerability. Finally discuss how the new code fixes the vulnerability.  

Assignment Details
Be sure you have carefully read and understand the materials in weeks 3 and 4.

1.      Select 2 CWE/SANS Top 25 vulnerabilities under the category of Risky Resource Management from one of these specific issues:  

a.       Buffer Copy without Checking Size of Input,  

b.       Improper Limitation of a Pathname to a Restricted Directory ,  

c.        Download of Code Without Integrity Check, and  

d.       Inclusion of Functionality from Untrusted Control Sphere.   

e.       Use of Potentially Dangerous Function

f.        Incorrect Calculation of Buffer Size

g.       Uncontrolled Format String

h.       Integer Overflow or Wraparound

Review and try the existing examples in links in the classroom.  Use AWS Cloud 9 to experiment. Work in multiple languages where possible.  

2.      Using AWS Cloud 9, create your own unique example for each of the 2 vulnerabilities in this category.  

3.      Your code examples do not need to large or fully functional from an application standpoint. However; they need to include all of the code such that the vulnerability can be fully explained and corrected.    

4.      Use the information in the CWE/SANS Top 25 vulnerabilities to understand and experiment.   

5.      Be sure your documentation and descriptions are detailed and completed.  

6.      You may need to conduct additional research to better understand the vulnerability or the features associated with a specific language.

More products