Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assignment to a method call of a tainted object #3

Open
rbonifacio opened this issue Apr 28, 2020 · 0 comments
Open

Assignment to a method call of a tainted object #3

rbonifacio opened this issue Apr 28, 2020 · 0 comments
Labels
bug Something isn't working

Comments

@rbonifacio
Copy link
Owner

rbonifacio commented Apr 28, 2020

In the current implementation, we are not propagating "taint information" when the RHS of an assignment is a method call of a tainted object. For instance, consider the example:

protected void doGet(HttpServletRequest req, HttpServletResponse resp) throws IOException {
   String str = req.getParameter("name");   /* str is TAINTED */ 
   PrintWriter writer = resp.getWriter();
   String str2 = str.toString();
   writer.println(str2);    /* BAD */
 }

Currently, we don't propagate the tainted information to the statement String str2 = str.toString()

@rbonifacio rbonifacio added the bug Something isn't working label Apr 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant