Juliet Java 1.0 Test suite #24
DownloadDescription
A collection of test cases in the Java language. It contains examples for 106 different CWEs. This software is not subject to copyright protection and is in the public domain. NIST assumes no responsibility whatsoever for its use by other parties, and makes no guaranties, expressed or implied, about its quality, reliability, or any other characteristic. All documents related to the Juliet Test Suite can be found at the documents page.
Documentation
Displaying test cases 6876 - 6900 of 14184 in total
-
CWE: 379 File Creation in Insecure Directory Sinks: perm GoodSink: securely create dir BadSink : permissions never set on dir Flow Variant: 11 Control flow: if(IO.static_returns_t()) and if(IO.static_returns_f())
-
CWE: 379 File Creation in Insecure Directory Sinks: perm GoodSink: securely create dir BadSink : permissions never set on dir Flow Variant: 12 Control flow: if(IO.static_returns_t_or_f())
-
CWE: 379 File Creation in Insecure Directory Sinks: perm GoodSink: securely create dir BadSink : permissions never set on dir Flow Variant: 13 Control flow: if(IO.static_final_five==5) and if(IO.static_final_five!=5)
-
CWE: 379 File Creation in Insecure Directory Sinks: perm GoodSink: securely create dir BadSink : permissions never set on dir Flow Variant: 14 Control flow: if(IO.static_five==5) and if(IO.static_five!=5)
-
CWE: 379 File Creation in Insecure Directory Sinks: perm GoodSink: securely create dir BadSink : permissions never set on dir Flow Variant: 15 Control flow: switch(7)
-
CWE: 379 File Creation in Insecure Directory Sinks: perm GoodSink: securely create dir BadSink : permissions never set on dir Flow Variant: 16 Control flow: while(true) and while(local_f)
-
CWE: 379 File Creation in Insecure Directory Sinks: perm GoodSink: securely create dir BadSink : permissions never set on dir Flow Variant: 17 Control flow: for loops
-
CWE: 379 File Creation in Insecure Directory Sinks: perm GoodSink: securely create dir BadSink : permissions never set on dir Flow Variant: 19 Control flow: Dead code after an if(true) return
-
CWE: 382 bad case calls System.exit during a normal work flow. Note: System.exit may be justifiable if a) significant failures occur during application initialization. b) the program is invoked by another application and intended to exit with a status code to determine success/failure. Other...
-
CWE: 382 bad case calls System.exit during a normal work flow. Note: System.exit may be justifiable if a) significant failures occur during application initialization. b) the program is invoked by another application and intended to exit with a status code to determine success/failure. Other...
-
CWE: 382 bad case calls System.exit during a normal work flow. Note: System.exit may be justifiable if a) significant failures occur during application initialization. b) the program is invoked by another application and intended to exit with a status code to determine success/failure. Other...
-
CWE: 382 bad case calls System.exit during a normal work flow. Note: System.exit may be justifiable if a) significant failures occur during application initialization. b) the program is invoked by another application and intended to exit with a status code to determine success/failure. Other...
-
CWE: 382 bad case calls System.exit during a normal work flow. Note: System.exit may be justifiable if a) significant failures occur during application initialization. b) the program is invoked by another application and intended to exit with a status code to determine success/failure. Other...
-
CWE: 382 bad case calls System.exit during a normal work flow. Note: System.exit may be justifiable if a) significant failures occur during application initialization. b) the program is invoked by another application and intended to exit with a status code to determine success/failure. Other...
-
CWE: 382 bad case calls System.exit during a normal work flow. Note: System.exit may be justifiable if a) significant failures occur during application initialization. b) the program is invoked by another application and intended to exit with a status code to determine success/failure. Other...
-
CWE: 382 bad case calls System.exit during a normal work flow. Note: System.exit may be justifiable if a) significant failures occur during application initialization. b) the program is invoked by another application and intended to exit with a status code to determine success/failure. Other...
-
CWE: 382 bad case calls System.exit during a normal work flow. Note: System.exit may be justifiable if a) significant failures occur during application initialization. b) the program is invoked by another application and intended to exit with a status code to determine success/failure. Other...
-
CWE: 382 bad case calls System.exit during a normal work flow. Note: System.exit may be justifiable if a) significant failures occur during application initialization. b) the program is invoked by another application and intended to exit with a status code to determine success/failure. Other...
-
CWE: 382 bad case calls System.exit during a normal work flow. Note: System.exit may be justifiable if a) significant failures occur during application initialization. b) the program is invoked by another application and intended to exit with a status code to determine success/failure. Other...
-
CWE: 382 bad case calls System.exit during a normal work flow. Note: System.exit may be justifiable if a) significant failures occur during application initialization. b) the program is invoked by another application and intended to exit with a status code to determine success/failure. Other...
-
CWE: 382 bad case calls System.exit during a normal work flow. Note: System.exit may be justifiable if a) significant failures occur during application initialization. b) the program is invoked by another application and intended to exit with a status code to determine success/failure. Other...
-
CWE: 382 bad case calls System.exit during a normal work flow. Note: System.exit may be justifiable if a) significant failures occur during application initialization. b) the program is invoked by another application and intended to exit with a status code to determine success/failure. Other...
-
CWE: 382 bad case calls System.exit during a normal work flow. Note: System.exit may be justifiable if a) significant failures occur during application initialization. b) the program is invoked by another application and intended to exit with a status code to determine success/failure. Other...
-
CWE: 382 bad case calls System.exit during a normal work flow. Note: System.exit may be justifiable if a) significant failures occur during application initialization. b) the program is invoked by another application and intended to exit with a status code to determine success/failure. Other...
-
CWE: 382 bad case calls System.exit during a normal work flow. Note: System.exit may be justifiable if a) significant failures occur during application initialization. b) the program is invoked by another application and intended to exit with a status code to determine success/failure. Other...