Deprecated test suite
Juliet C/C++ 1.0 with extra support Test suite #68
DownloadDescription
This is a collection of test cases in the C/C++ language. It contains examples for 116 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 15426 - 15450 of 45309 in total
-
CWE: 188 Reliance on Data Memory Layout Sinks: modify_local GoodSink: Modify the second field of the struct using the field name BadSink : Attempt to modify second field in struct, assuming the first field is an int Flow Variant: 07 Control flow: if(static_five==5) and if(static_five!=5)
-
CWE: 188 Reliance on Data Memory Layout Sinks: modify_local GoodSink: Modify the second field of the struct using the field name BadSink : Attempt to modify second field in struct, assuming the first field is an int Flow Variant: 08 Control flow: if(static_returns_t()) and if(static_returns_f())
-
CWE: 188 Reliance on Data Memory Layout Sinks: modify_local GoodSink: Modify the second field of the struct using the field name BadSink : Attempt to modify second field in struct, assuming the first field is an int Flow Variant: 09 Control flow: if(global_const_t) and if(global_const_f)
-
CWE: 188 Reliance on Data Memory Layout Sinks: modify_local GoodSink: Modify the second field of the struct using the field name BadSink : Attempt to modify second field in struct, assuming the first field is an int Flow Variant: 10 Control flow: if(global_t) and if(global_f)
-
CWE: 188 Reliance on Data Memory Layout Sinks: modify_local GoodSink: Modify the second field of the struct using the field name BadSink : Attempt to modify second field in struct, assuming the first field is an int Flow Variant: 11 Control flow: if(global_returns_t()) and if(global_returns_f())
-
CWE: 188 Reliance on Data Memory Layout Sinks: modify_local GoodSink: Modify the second field of the struct using the field name BadSink : Attempt to modify second field in struct, assuming the first field is an int Flow Variant: 12 Control flow: if(global_returns_t_or_f())
-
CWE: 188 Reliance on Data Memory Layout Sinks: modify_local GoodSink: Modify the second field of the struct using the field name BadSink : Attempt to modify second field in struct, assuming the first field is an int Flow Variant: 13 Control flow: if(global_const_five==5) and if(global_const_f...
-
CWE: 188 Reliance on Data Memory Layout Sinks: modify_local GoodSink: Modify the second field of the struct using the field name BadSink : Attempt to modify second field in struct, assuming the first field is an int Flow Variant: 14 Control flow: if(global_five==5) and if(global_five!=5)
-
CWE: 188 Reliance on Data Memory Layout Sinks: modify_local GoodSink: Modify the second field of the struct using the field name BadSink : Attempt to modify second field in struct, assuming the first field is an int Flow Variant: 15 Control flow: switch(6)
-
CWE: 188 Reliance on Data Memory Layout Sinks: modify_local GoodSink: Modify the second field of the struct using the field name BadSink : Attempt to modify second field in struct, assuming the first field is an int Flow Variant: 16 Control flow: while(1) and while(0)
-
CWE: 188 Reliance on Data Memory Layout Sinks: modify_local GoodSink: Modify the second field of the struct using the field name BadSink : Attempt to modify second field in struct, assuming the first field is an int Flow Variant: 17 Control flow: for loops
-
CWE: 188 Reliance on Data Memory Layout Sinks: modify_local GoodSink: Modify the second field of the struct using the field name BadSink : Attempt to modify second field in struct, assuming the first field is an int Flow Variant: 18 Control flow: goto statements
-
CWE: 188 Reliance on Data Memory Layout Sinks: modify_local GoodSink: Modify the second field of the struct using the field name BadSink : Attempt to modify second field in struct, assuming the first field is an int Flow Variant: 19 Control flow: Dead code after a return
-
CWE: 188 Reliance on Data Memory Layout Sinks: union GoodSink: Use mechanisms that are not dependent upon size, alignment/packing, or byte order to accomplish equivalent functionality BadSink : Modify a union member by relying on the byte-order, size, alignment/packing of struct and union fiel...
-
CWE: 188 Reliance on Data Memory Layout Sinks: union GoodSink: Use mechanisms that are not dependent upon size, alignment/packing, or byte order to accomplish equivalent functionality BadSink : Modify a union member by relying on the byte-order, size, alignment/packing of struct and union fiel...
-
CWE: 188 Reliance on Data Memory Layout Sinks: union GoodSink: Use mechanisms that are not dependent upon size, alignment/packing, or byte order to accomplish equivalent functionality BadSink : Modify a union member by relying on the byte-order, size, alignment/packing of struct and union fiel...
-
CWE: 188 Reliance on Data Memory Layout Sinks: union GoodSink: Use mechanisms that are not dependent upon size, alignment/packing, or byte order to accomplish equivalent functionality BadSink : Modify a union member by relying on the byte-order, size, alignment/packing of struct and union fiel...
-
CWE: 188 Reliance on Data Memory Layout Sinks: union GoodSink: Use mechanisms that are not dependent upon size, alignment/packing, or byte order to accomplish equivalent functionality BadSink : Modify a union member by relying on the byte-order, size, alignment/packing of struct and union fiel...
-
CWE: 188 Reliance on Data Memory Layout Sinks: union GoodSink: Use mechanisms that are not dependent upon size, alignment/packing, or byte order to accomplish equivalent functionality BadSink : Modify a union member by relying on the byte-order, size, alignment/packing of struct and union fiel...
-
CWE: 188 Reliance on Data Memory Layout Sinks: union GoodSink: Use mechanisms that are not dependent upon size, alignment/packing, or byte order to accomplish equivalent functionality BadSink : Modify a union member by relying on the byte-order, size, alignment/packing of struct and union fiel...
-
CWE: 188 Reliance on Data Memory Layout Sinks: union GoodSink: Use mechanisms that are not dependent upon size, alignment/packing, or byte order to accomplish equivalent functionality BadSink : Modify a union member by relying on the byte-order, size, alignment/packing of struct and union fiel...
-
CWE: 188 Reliance on Data Memory Layout Sinks: union GoodSink: Use mechanisms that are not dependent upon size, alignment/packing, or byte order to accomplish equivalent functionality BadSink : Modify a union member by relying on the byte-order, size, alignment/packing of struct and union fiel...
-
CWE: 188 Reliance on Data Memory Layout Sinks: union GoodSink: Use mechanisms that are not dependent upon size, alignment/packing, or byte order to accomplish equivalent functionality BadSink : Modify a union member by relying on the byte-order, size, alignment/packing of struct and union fiel...
-
CWE: 188 Reliance on Data Memory Layout Sinks: union GoodSink: Use mechanisms that are not dependent upon size, alignment/packing, or byte order to accomplish equivalent functionality BadSink : Modify a union member by relying on the byte-order, size, alignment/packing of struct and union fiel...
-
CWE: 188 Reliance on Data Memory Layout Sinks: union GoodSink: Use mechanisms that are not dependent upon size, alignment/packing, or byte order to accomplish equivalent functionality BadSink : Modify a union member by relying on the byte-order, size, alignment/packing of struct and union fiel...