diff --git a/java/ql/src/experimental/Security/CWE/CWE-600/UncaughtServletException.qhelp b/java/ql/src/experimental/Security/CWE/CWE-600/UncaughtServletException.qhelp index de9d395e731..cf04705eecd 100644 --- a/java/ql/src/experimental/Security/CWE/CWE-600/UncaughtServletException.qhelp +++ b/java/ql/src/experimental/Security/CWE/CWE-600/UncaughtServletException.qhelp @@ -2,7 +2,7 @@

- Even though the request-handling methods of Servlet are declared throws IOException, ServletException, it's a bad idea to let such exceptions be thrown. Failure to catch exceptions in a servlet could leave a system in an unexpected state, possibly resulting in denial-of-service attacks, or could lead to exposure of sensitive information because when a servlet throws an exception, the servlet container typically sends debugging information back to the user. That information could be valuable to an attacker. + Even though the request-handling methods of Servlet are declared throws IOException, ServletException, it's a bad idea to let such exceptions be thrown. Failure to catch exceptions in a servlet could lead to exposure of sensitive information because when a servlet throws an exception, the servlet container typically sends debugging information back to the user. That information could be valuable to an attacker.