From 368572f1f066b6237201210d17de95b9903a520e Mon Sep 17 00:00:00 2001 From: Luke Cartey <5377966+lcartey@users.noreply.github.com> Date: Tue, 4 Aug 2020 09:40:59 +0100 Subject: [PATCH] Update java/ql/src/Security/CWE/CWE-020/UntrustedDataToExternalAPI.qhelp Co-authored-by: Marcono1234 --- .../src/Security/CWE/CWE-020/UntrustedDataToExternalAPI.qhelp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/java/ql/src/Security/CWE/CWE-020/UntrustedDataToExternalAPI.qhelp b/java/ql/src/Security/CWE/CWE-020/UntrustedDataToExternalAPI.qhelp index 855d0ca30e4..02f754cfd56 100644 --- a/java/ql/src/Security/CWE/CWE-020/UntrustedDataToExternalAPI.qhelp +++ b/java/ql/src/Security/CWE/CWE-020/UntrustedDataToExternalAPI.qhelp @@ -46,7 +46,7 @@ some existing sanitization.

-

If the query reported the call to StringBuilder.append on Line 7, this would suggest that this external API is +

If the query reported the call to StringBuilder.append on line 7, this would suggest that this external API is not currently modeled as a taint step in the taint tracking library. The next step would be to model this as taint step, then re-run the query to determine what additional results might be found. In this example, it seems likely that the result of the StringBuilder will be executed as an SQL query, potentially leading to an SQL injection vulnerability.