CS 390S: Secure Programming

Labs

• Use the National Vulnerability Database to find a buffer overflow in an open source product
• Find the lines of code responsible for the vulnerability
  
• Suggest new code to fix the issue

1. The CVE identifier and CVE description
2. The URL where you found the code
3. The vulnerable code
4. An explanation of why it's vulnerable
5. Your code fix
6. How long it took you to do this (as course workload feedback, not graded)

• Avoid vulnerabilities found in real shells
• Implement umask

1. A list of the security functional requirements you managed to implement
2. A description of how you managed to implement them
3. The tests you used to make sure your implementation worked, and their output. The completeness and appropriateness of your tests will be graded.
4. The relevant code
5. How long it took you to do this (as course workload feedback, not graded)