Juliet Java 1.3 with extra support Test suite #109
DownloadDescription
A collection of Java test cases updated from Juliet 1.2
Documentation
Displaying test cases 22451 - 22475 of 28881 in total
-
CWE: 81 Cross Site Scripting (XSS) in Error Message BadSource: listen_tcp Read data using a listening tcp connection GoodSource: A hardcoded string BadSink: sendErrorServlet XSS in sendError Flow Variant: 42 Data flow: data returned from one method to another in the same class
-
CWE: 81 Cross Site Scripting (XSS) in Error Message BadSource: listen_tcp Read data using a listening tcp connection GoodSource: A hardcoded string Sinks: sendErrorServlet BadSink : XSS in sendError Flow Variant: 45 Data flow: data passed as a private class member variable from one function ...
-
CWE: 81 Cross Site Scripting (XSS) in Error Message BadSource: listen_tcp Read data using a listening tcp connection GoodSource: A hardcoded string BadSink: sendErrorServlet XSS in sendError Flow Variant: 51 Data flow: data passed as an argument from one function to another in different class...
-
CWE: 81 Cross Site Scripting (XSS) in Error Message BadSource: listen_tcp Read data using a listening tcp connection GoodSource: A hardcoded string Sinks: sendErrorServlet BadSink : XSS in sendError Flow Variant: 52 Data flow: data passed as an argument from one method to another to another ...
-
CWE: 81 Cross Site Scripting (XSS) in Error Message BadSource: listen_tcp Read data using a listening tcp connection GoodSource: A hardcoded string Sinks: sendErrorServlet BadSink : XSS in sendError Flow Variant: 53 Data flow: data passed as an argument from one method through two others to ...
-
CWE: 81 Cross Site Scripting (XSS) in Error Message BadSource: listen_tcp Read data using a listening tcp connection GoodSource: A hardcoded string Sinks: sendErrorServlet BadSink : XSS in sendError Flow Variant: 54 Data flow: data passed as an argument from one method through three others t...
-
CWE: 81 Cross Site Scripting (XSS) in Error Message BadSource: listen_tcp Read data using a listening tcp connection GoodSource: A hardcoded string Sinks: sendErrorServlet BadSink : XSS in sendError Flow Variant: 61 Data flow: data returned from one method to another in different classes in ...
-
CWE: 81 Cross Site Scripting (XSS) in Error Message BadSource: listen_tcp Read data using a listening tcp connection GoodSource: A hardcoded string Sinks: sendErrorServlet BadSink : XSS in sendError Flow Variant: 66 Data flow: data passed in an array from one method to another in different s...
-
CWE: 81 Cross Site Scripting (XSS) in Error Message BadSource: listen_tcp Read data using a listening tcp connection GoodSource: A hardcoded string Sinks: sendErrorServlet BadSink : XSS in sendError Flow Variant: 67 Data flow: data passed in a class from one method to another in different so...
-
CWE: 81 Cross Site Scripting (XSS) in Error Message BadSource: listen_tcp Read data using a listening tcp connection GoodSource: A hardcoded string BadSink: sendErrorServlet XSS in sendError Flow Variant: 68 Data flow: data passed as a member variable in the a class, which is used by a method...
-
CWE: 81 Cross Site Scripting (XSS) in Error Message BadSource: listen_tcp Read data using a listening tcp connection GoodSource: A hardcoded string Sinks: sendErrorServlet BadSink : XSS in sendError Flow Variant: 71 Data flow: data passed as an Object reference argument from one method to an...
-
CWE: 81 Cross Site Scripting (XSS) in Error Message BadSource: listen_tcp Read data using a listening tcp connection GoodSource: A hardcoded string Sinks: sendErrorServlet BadSink : XSS in sendError Flow Variant: 72 Data flow: data passed in a Vector from one method to another in different s...
-
CWE: 81 Cross Site Scripting (XSS) in Error Message BadSource: listen_tcp Read data using a listening tcp connection GoodSource: A hardcoded string Sinks: sendErrorServlet BadSink : XSS in sendError Flow Variant: 73 Data flow: data passed in a LinkedList from one method to another in differe...
-
CWE: 81 Cross Site Scripting (XSS) in Error Message BadSource: listen_tcp Read data using a listening tcp connection GoodSource: A hardcoded string Sinks: sendErrorServlet BadSink : XSS in sendError Flow Variant: 74 Data flow: data passed in a HashMap from one method to another in different ...
-
CWE: 81 Cross Site Scripting (XSS) in Error Message BadSource: listen_tcp Read data using a listening tcp connection GoodSource: A hardcoded string Sinks: sendErrorServlet BadSink : XSS in sendError Flow Variant: 75 Data flow: data passed in a serialized object from one method to another in ...
-
CWE: 81 Cross Site Scripting (XSS) in Error Message BadSource: listen_tcp Read data using a listening tcp connection GoodSource: A hardcoded string Sinks: sendErrorServlet BadSink : XSS in sendError Flow Variant: 81 Data flow: data passed in a parameter to an abstract method
-
Demonstrates use of unlock() more times than lock() in a Servlet that updates a shared variable. Servlets are inherently multithreaded, so we dont need to actually start threads in the bad() and goodX() functions.
-
Demonstrates use of unlock() on a lock that is not locked in multithreaded code that accesses a shared variable.
-
Demonstrates a deadlock caused by obtaining locks in a different order in different functions in a Servlet that accesses shared variables. Servlets are inherently multithreaded, so we dont need to actually start threads in the bad() and goodX() functions.
-
Demonstrates a deadlock caused by obtaining locks in a different order in different functions in multithreaded code that accesses shared variables.
-
Demonstrates a deadlock caused by synchronizing on objects in a different order in different functions in a Servlet that accesses shared variables. Servlets are inherently multithreaded, so we dont need to actually start threads in the bad() and goodX() functions.
-
Demonstrates a deadlock caused by synchronizing on objects in a different order in different functions in multithreaded code that accesses shared variables.
-
Demonstrates a deadlock caused by synchronized methods in objects that call one another in a Servlet. Servlets are inherently multithreaded, so we dont need to actually start threads in the bad() and goodX() functions. Implementation based on http://download.oracle.com/javase/tutorial/essential...
-
Demonstrates a deadlock caused by synchronized methods in objects that call one another in multithreaded code. Implementation based on http://download.oracle.com/javase/tutorial/essential/concurrency/deadlock.html.
-
Infinite loop - do{}while()