Displaying test cases 34251 - 34275 of 45437 in total
-
CWE: 190 Integer Overflow BadSource: fscanf Read data from the console using fscanf() GoodSource: Set data to a small, non-zero number (two) Sinks: add GoodSink: Ensure there will not be an overflow before adding 1 to data BadSink : Add 1 to data, which can cause an overflow Flow Variant: 1...
-
CWE: 190 Integer Overflow BadSource: fscanf Read data from the console using fscanf() GoodSource: Set data to a small, non-zero number (two) Sinks: add GoodSink: Ensure there will not be an overflow before adding 1 to data BadSink : Add 1 to data, which can cause an overflow Flow Variant: 1...
-
CWE: 190 Integer Overflow BadSource: fscanf Read data from the console using fscanf() GoodSource: Set data to a small, non-zero number (two) Sinks: add GoodSink: Ensure there will not be an overflow before adding 1 to data BadSink : Add 1 to data, which can cause an overflow Flow Variant: 0...
-
CWE: 190 Integer Overflow BadSource: fscanf Read data from the console using fscanf() GoodSource: Set data to a small, non-zero number (two) Sinks: add GoodSink: Ensure there will not be an overflow before adding 1 to data BadSink : Add 1 to data, which can cause an overflow Flow Variant: 0...
-
CWE: 190 Integer Overflow BadSource: fscanf Read data from the console using fscanf() GoodSource: Set data to a small, non-zero number (two) Sinks: add GoodSink: Ensure there will not be an overflow before adding 1 to data BadSink : Add 1 to data, which can cause an overflow Flow Variant: 0...
-
CWE: 190 Integer Overflow BadSource: fscanf Read data from the console using fscanf() GoodSource: Set data to a small, non-zero number (two) Sinks: add GoodSink: Ensure there will not be an overflow before adding 1 to data BadSink : Add 1 to data, which can cause an overflow Flow Variant: 0...
-
CWE: 190 Integer Overflow BadSource: fscanf Read data from the console using fscanf() GoodSource: Set data to a small, non-zero number (two) Sinks: add GoodSink: Ensure there will not be an overflow before adding 1 to data BadSink : Add 1 to data, which can cause an overflow Flow Variant: 0...
-
CWE: 190 Integer Overflow BadSource: fscanf Read data from the console using fscanf() GoodSource: Set data to a small, non-zero number (two) Sinks: add GoodSink: Ensure there will not be an overflow before adding 1 to data BadSink : Add 1 to data, which can cause an overflow Flow Variant: 0...
-
CWE: 190 Integer Overflow BadSource: fscanf Read data from the console using fscanf() GoodSource: Set data to a small, non-zero number (two) Sinks: add GoodSink: Ensure there will not be an overflow before adding 1 to data BadSink : Add 1 to data, which can cause an overflow Flow Variant: 0...
-
CWE: 190 Integer Overflow BadSource: fscanf Read data from the console using fscanf() GoodSource: Set data to a small, non-zero number (two) Sinks: add GoodSink: Ensure there will not be an overflow before adding 1 to data BadSink : Add 1 to data, which can cause an overflow Flow Variant: 0...
-
CWE: 190 Integer Overflow BadSource: fscanf Read data from the console using fscanf() GoodSource: Set data to a small, non-zero number (two) Sinks: add GoodSink: Ensure there will not be an overflow before adding 1 to data BadSink : Add 1 to data, which can cause an overflow Flow Variant: 0...
-
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...
-
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...