Displaying test cases 46401 - 46425 of 46447 in total
-
Authorization is given by an hard-coded password, which is built into the code. So it can be read from a copy, be changed easily, and every copy of the code uses the same one.
-
Authorization is given by an hard-coded password, which is built into the code. So it can be read from a copy, be changed easily, and every copy of the code uses the same one.
-
Authorization is given by an hard-coded password, which is built into the code. So it can be read from a copy, be changed easily, and every copy of the code uses the same one.
-
Authorization is given by an hard-coded password, which is built into the code. So it can be read from a copy, be changed easily, and every copy of the code uses the same one.
-
The code, with a container complexity, creates a file from data read, without filtering.
-
The code, with a scope complexity, creates a file from data read, without filtering.
-
The code creates a file from data read, without filtering.
-
The code, with a loop structure complexity, tries to execute a system command, read from the input buffer, without any validation.
-
The code, with a local control flow complexity, tries to execute a system command, read from the input buffer, without any validation.
-
The code, with a scope complexity, tries to execute a system command, read from the input buffer, without any validation.
-
The code tries to execute a system command, read from the input buffer, without any validation.
-
The test cases shows hard-coded password is not used.
-
The test cases shows hard-coded password is not used.
-
The test cases shows hard-coded password is used.
-
Test of tool\'s ability to identify an assignment of public data to to a private array field.
-
Private Array-Typed field returned from a public method.
-
Test of tool ability to identify an unchecked (unhandled) exception in Java.
-
Test determines if a tool can identify a hardcoded password weakness in code.
-
Test of tool to identify potential resource injection weakness in source code.
-
Test of tool\'s ability to identify potential resource injection in code.
-
Test to verify that a tool identifies a potential path manipulation code weakness.
-
Tainted output allows cross-site scripting attack. (fixed version 2)
-
Tainted output allows cross-site scripting attack.
-
Tainted output allows cross-site scripting attack.
-
An unsafe function is used causing the entire container to exit.