[cs631apue] Test Cases and C Vulnerabilities
Charles Magyar IV
cmagyar at stevens.edu
Wed Sep 2 09:19:46 EDT 2020
>From my quick research, it looks like gcc has a flag to detect stack smashing, which may be default. After work I'll try to reproduce the issue shown in the first link below and get back to you.
The third link has some stuff about string manipulation and other attacks. You may find it interesting, although you might already be familiar with most of it.
I'm quite interested in learning security as well, so if you find anything cool or have good references please share!
From: cs631apue-bounces at lists.stevens.edu <cs631apue-bounces at lists.stevens.edu> on behalf of Liam Brew <lbrew at stevens.edu>
Sent: Tuesday, September 1, 2020 9:05 AM
To: cs631apue at lists.stevens.edu <cs631apue at lists.stevens.edu>
Subject: [cs631apue] Test Cases and C Vulnerabilities
It was nice to meet everyone yesterday. I’m looking forward to a good semester together. As this is my first course that deals primarily with C, I was wondering how this language’s code is typically evaluated in an academic setting. While I assume test cases such as erroneous inputs are very likely, I’m not sure about more malicious ones such as stack smashing/overflows, string manipulations, and so on. If anyone can chime in with their experiences, maybe we can compile a solid list of cases to consider so that there are less surprises grading-wise.
Thanks! See you soon.
B.E. Software Engineering 2021
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cs631apue