From 45574d4eaa2900032ef6302bebdc04c2193016e6 Mon Sep 17 00:00:00 2001 From: Max Schaefer Date: Wed, 28 Nov 2018 13:53:28 +0000 Subject: [PATCH] JavaScript: Minor change to documentation to facilitate opening another PR. --- .../src/Security/CWE-754/UnvalidatedDynamicMethodCall.qhelp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/javascript/ql/src/Security/CWE-754/UnvalidatedDynamicMethodCall.qhelp b/javascript/ql/src/Security/CWE-754/UnvalidatedDynamicMethodCall.qhelp index 14a2e49ee1d..a313a23706b 100644 --- a/javascript/ql/src/Security/CWE-754/UnvalidatedDynamicMethodCall.qhelp +++ b/javascript/ql/src/Security/CWE-754/UnvalidatedDynamicMethodCall.qhelp @@ -11,8 +11,8 @@ could choose a name that makes the application invoke an unexpected method, whic exception. If this exception is not handled, it could be used to mount a denial-of-service attack.

-For example, there might not be a method of the given name or the result of the lookup might not be -a function, which would cause the method call to throw a TypeError at runtime. +For example, there might not be a method of the given name, or the result of the lookup might not be +a function. In either case the method call will throw a TypeError at runtime.

Another, more subtle example is where the result of the lookup is a standard library method from