Deprecated test suite
Juliet Java 1.0 with extra support Test suite #69
DownloadDescription
This is a collection of test cases in the Java language. It contains examples for 106 different CWEs. NOTE: This package contains only individual test cases. We recommend to download the full test suite at the top of the "Test Suite" page. All documents related to the Juliet Test Suite can be found at the documents page
Displaying test cases 6976 - 7000 of 14184 in total
-
CWE: 395 An object may be null when asked to perform a method; a catch block for NullPointerException is used instead of checking for null objects in the code Sinks: GoodSink: check for null reference before taking action BadSink : using catch to detect null references Flow Variant: 03 Contro...
-
CWE: 395 An object may be null when asked to perform a method; a catch block for NullPointerException is used instead of checking for null objects in the code Sinks: GoodSink: check for null reference before taking action BadSink : using catch to detect null references Flow Variant: 04 Contro...
-
CWE: 395 An object may be null when asked to perform a method; a catch block for NullPointerException is used instead of checking for null objects in the code Sinks: GoodSink: check for null reference before taking action BadSink : using catch to detect null references Flow Variant: 05 Contro...
-
CWE: 395 An object may be null when asked to perform a method; a catch block for NullPointerException is used instead of checking for null objects in the code Sinks: GoodSink: check for null reference before taking action BadSink : using catch to detect null references Flow Variant: 06 Contro...
-
CWE: 395 An object may be null when asked to perform a method; a catch block for NullPointerException is used instead of checking for null objects in the code Sinks: GoodSink: check for null reference before taking action BadSink : using catch to detect null references Flow Variant: 07 Contro...
-
CWE: 395 An object may be null when asked to perform a method; a catch block for NullPointerException is used instead of checking for null objects in the code Sinks: GoodSink: check for null reference before taking action BadSink : using catch to detect null references Flow Variant: 08 Contro...
-
CWE: 395 An object may be null when asked to perform a method; a catch block for NullPointerException is used instead of checking for null objects in the code Sinks: GoodSink: check for null reference before taking action BadSink : using catch to detect null references Flow Variant: 09 Contro...
-
CWE: 395 An object may be null when asked to perform a method; a catch block for NullPointerException is used instead of checking for null objects in the code Sinks: GoodSink: check for null reference before taking action BadSink : using catch to detect null references Flow Variant: 10 Contro...
-
CWE: 395 An object may be null when asked to perform a method; a catch block for NullPointerException is used instead of checking for null objects in the code Sinks: GoodSink: check for null reference before taking action BadSink : using catch to detect null references Flow Variant: 11 Contro...
-
CWE: 395 An object may be null when asked to perform a method; a catch block for NullPointerException is used instead of checking for null objects in the code Sinks: GoodSink: check for null reference before taking action BadSink : using catch to detect null references Flow Variant: 12 Contro...
-
CWE: 395 An object may be null when asked to perform a method; a catch block for NullPointerException is used instead of checking for null objects in the code Sinks: GoodSink: check for null reference before taking action BadSink : using catch to detect null references Flow Variant: 13 Contro...
-
CWE: 395 An object may be null when asked to perform a method; a catch block for NullPointerException is used instead of checking for null objects in the code Sinks: GoodSink: check for null reference before taking action BadSink : using catch to detect null references Flow Variant: 14 Contro...
-
CWE: 395 An object may be null when asked to perform a method; a catch block for NullPointerException is used instead of checking for null objects in the code Sinks: GoodSink: check for null reference before taking action BadSink : using catch to detect null references Flow Variant: 15 Contro...
-
CWE: 395 An object may be null when asked to perform a method; a catch block for NullPointerException is used instead of checking for null objects in the code Sinks: GoodSink: check for null reference before taking action BadSink : using catch to detect null references Flow Variant: 16 Contro...
-
CWE: 395 An object may be null when asked to perform a method; a catch block for NullPointerException is used instead of checking for null objects in the code Sinks: GoodSink: check for null reference before taking action BadSink : using catch to detect null references Flow Variant: 17 Contro...
-
CWE: 395 An object may be null when asked to perform a method; a catch block for NullPointerException is used instead of checking for null objects in the code Sinks: GoodSink: check for null reference before taking action BadSink : using catch to detect null references Flow Variant: 19 Contro...
-
CWE: 396 An overly broad catch statement may cause errors in program execution if unexpected exceptions are thrown Sinks: Exception GoodSink: Catch specific exception type (NumberFormatException) BadSink : Catch Exception, which is overly generic Flow Variant: 01 Baseline
-
CWE: 396 An overly broad catch statement may cause errors in program execution if unexpected exceptions are thrown Sinks: Exception GoodSink: Catch specific exception type (NumberFormatException) BadSink : Catch Exception, which is overly generic Flow Variant: 02 Control flow: if(true) and if...
-
CWE: 396 An overly broad catch statement may cause errors in program execution if unexpected exceptions are thrown Sinks: Exception GoodSink: Catch specific exception type (NumberFormatException) BadSink : Catch Exception, which is overly generic Flow Variant: 03 Control flow: if(5==5) and if...
-
CWE: 396 An overly broad catch statement may cause errors in program execution if unexpected exceptions are thrown Sinks: Exception GoodSink: Catch specific exception type (NumberFormatException) BadSink : Catch Exception, which is overly generic Flow Variant: 04 Control flow: if(private_fina...
-
CWE: 396 An overly broad catch statement may cause errors in program execution if unexpected exceptions are thrown Sinks: Exception GoodSink: Catch specific exception type (NumberFormatException) BadSink : Catch Exception, which is overly generic Flow Variant: 05 Control flow: if(private_t) a...
-
CWE: 396 An overly broad catch statement may cause errors in program execution if unexpected exceptions are thrown Sinks: Exception GoodSink: Catch specific exception type (NumberFormatException) BadSink : Catch Exception, which is overly generic Flow Variant: 06 Control flow: if(private_fina...
-
CWE: 396 An overly broad catch statement may cause errors in program execution if unexpected exceptions are thrown Sinks: Exception GoodSink: Catch specific exception type (NumberFormatException) BadSink : Catch Exception, which is overly generic Flow Variant: 07 Control flow: if(private_five...
-
CWE: 396 An overly broad catch statement may cause errors in program execution if unexpected exceptions are thrown Sinks: Exception GoodSink: Catch specific exception type (NumberFormatException) BadSink : Catch Exception, which is overly generic Flow Variant: 08 Control flow: if(private_retu...
-
CWE: 396 An overly broad catch statement may cause errors in program execution if unexpected exceptions are thrown Sinks: Exception GoodSink: Catch specific exception type (NumberFormatException) BadSink : Catch Exception, which is overly generic Flow Variant: 09 Control flow: if(IO.static_fi...