Displaying test cases 44051 - 44075 of 45437 in total
-
Since the argument (the file name) is not validated, one can open every file and print it.
-
The test case shows a possible variant of an improper pointer subtraction. The code works well if you assume that the two integers are contiguously allocated in the memory, which is not always the case.
-
The test case shows an improper null termination with a buffer address type complexity.
-
The test case shows an improper null termination with a buffer address type complexity.
-
The arguments are not validated so, one can include a bad argument such as /etc/passwd in the list of files to print out.
-
The arguments are not validated so, one can include a bad argument such as /etc/passwd in the list of files to print out.
-
Since the argument (the file name) is not validated, one can open every file and print it.
-
Cross-Site Scripting in C. This is a CGI program which take some parameters values then print it.
-
Cross-Site Scripting in C. This is a CGI program which take some parameters values then print it.
-
Use of Dangerous Process Creation Function [em]execlp[/em]
-
The accidental deletion of a data-structure sentinel can cause serious programing logic problems. (from CLASP TCCLASP-5_6_6_10)
-
If a function\'s return value is not properly checked, the function could have failed without proper acknowledgement. (from CLASP TCCLASP-5_6_3_10)
-
The use of a hard-coded cryptographic key tremendously increases the possibility that encrypted data may be recovered (from TCCLASP-5_5_10_10-C)
-
An unsigned-to-signed conversion error takes place when a large unsignedprimitive is used as an signed value - usually as a size variable. (from TCCLASP-5_2_12_10) Duplicate code of Test Case 19
-
Sometimes an error is detected, and bad or no action is taken. (from TCCLASP-5_6_19_10)
-
Assumptions about protocol data or data stored in memory can be invalid, resulting in using data in ways that were unintended. (from TCCLASP-5_3_1_10)
-
Simple test of tool ability to identify a double free weakness.
-
Test of tool ability to identify a memory leak.
-
Test of tool ability to identify a potentil write-what-where weakness in code.
-
Test of tool ability to identify improper pointer subtraction.
-
write-what-where error
-
type errors
-
integer underflow error (wrap or wraparound)
-
integer overflow error(wrap or wraparound)
-
signed-to-unsigned error