| Memory error | Memory leak | example2.c | main | 20 | 4 | Potential leak of memory pointed to by 'name' | View Report |
| Security | Potential buffer overflow in call to 'gets' | example1.c | main | 17 | 1 | Call to function 'gets' is extremely insecure as it can always result in a buffer overflow | View Report |
| Security | Potential buffer overflow in call to 'gets' | example3.c | main | 14 | 1 | Call to function 'gets' is extremely insecure as it can always result in a buffer overflow | View Report |
| Security | Potential buffer overflow in call to 'gets' | example2.c | main | 16 | 1 | Call to function 'gets' is extremely insecure as it can always result in a buffer overflow | View Report |
| Security | Potential insecure memory buffer bounds restriction in call 'strcpy' | example2.c | main | 14 | 1 | Call to function 'strcpy' is insecure as it does not provide bounding of the memory buffer. Replace unbounded copy functions with analogous functions that support length arguments such as 'strlcpy'. CWE-119 | View Report |
| Security | Potential insecure memory buffer bounds restriction in call 'strcpy' | example1.c | main | 13 | 1 | Call to function 'strcpy' is insecure as it does not provide bounding of the memory buffer. Replace unbounded copy functions with analogous functions that support length arguments such as 'strlcpy'. CWE-119 | View Report |