JAVA.IO.INJ.CODE : Code Injection (Java)

JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.

If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.

If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.

If you access the manual through the hub's Web GUI, the functionality will not be suppressed because the hub is a web server.
Alternatively, your browser may allow you to explicitly disable the security setting that suppresses functionality. See the CodeSonar FAQ for more information.

CodeSonar^® 9.2p0

CONFIDENTIAL

CodeSecure Inc

JAVA.IO.INJ.CODE : Code Injection (Java)

Summary

Tainted data flows into a field annotated as @CodeTrusted, or into a into a script execution routine.

Checks for this class use the CodeSonar Java taint analysis. See Taint Tracking for CodeSonar Java Warning Classes for more information on this analysis, including lists of the methods that CodeSonar automatically recognizes as relevant and information about specifying additional methods that CodeSonar should recognize as taint sources, sinks, or sanitizers.

Use configuration parameter JAVA_ANALYSIS_ADVANCED_INJECTION to specify the level of checking to perform for this and other taint-related warning classes:

Properties

Example

import java.io.IOException;
import java.io.PrintWriter;

import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;

import com.juliasoft.julia.checkers.injection.SqlTrusted;
import com.juliasoft.julia.checkers.injection.Trusted;

@SuppressWarnings("serial")
public class BasicInjection extends HttpServlet {
  private @SqlTrusted Object sqlTrusted;
  private @Trusted Object trusted;
  public String a = "my friend";

  @Override
  protected final void doGet(HttpServletRequest request, HttpServletResponse response) throws IOException {
    processRequest(request, response);
  }

  private void test2(@SqlTrusted String s) {}

  private void test3(@Trusted String s) {}

  private void processRequest(HttpServletRequest request, HttpServletResponse response) throws IOException {
    response.setContentType("text/html;charset=UTF-8");

    String user = request.getParameter("user");              // The value of variable 'user' is obtained from user input
      out.println(user);                                     // and is therefore treated as tainted.

    try (PrintWriter out = response.getWriter()) {
      out.println("User : " + user); // Cross Site Scripting (Java) warning issued here
      out.println(user);             // Cross Site Scripting (Java) warning issued here
      out.println("hello");
      out.println("hello " + a);
    }

    if (user != null)
      test2(user);                   // SQL Injection (Java) warning issued here
    test2("User: " + user);          // SQL Injection (Java) warning issued here
    test2("hello");
    test2("hello " + a);
    test3(user);                     // Tainted @Trusted Value (Java) warning issued here
    test3("User: " + user);          // Tainted @Trusted Value (Java) warning issued here
    test3("hello");
    test3("hello " + a);
    sqlTrusted = user;               // SQL Injection (Java) warning issued here
    trusted = user;                  // Tainted @Trusted Value (Java) warning issued here
    sqlTrusted = "User: " + user;    // SQL Injection (Java) warning issued here
    trusted = "User: " + user;       // Tainted @Trusted Value (Java) warning issued here
    sqlTrusted = "hello";
    trusted = "hello";
    sqlTrusted = "hello " + a;
    trusted = "hello " + a;
  }
}

Resolution

Verify that a security error actually corresponds to unconstrained information flow from source locations into sink locations. If this is the case, add a sanitizing algorithm to clean data before it flows into sinks, or use safe statements to propagate data inside the program.

Relevant Configuration File Parameters

The following configuration file parameters affect checks for this warning class.