Skip to content

Commit 26908ea

Browse files
felicitymayguntrip
andauthored
Update docs/codeql/codeql-language-guides/using-flow-labels-for-precise-data-flow-analysis.rst
Co-authored-by: Steve Guntrip <[email protected]>
1 parent 9eafee3 commit 26908ea

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/codeql/codeql-language-guides/using-flow-labels-for-precise-data-flow-analysis.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -390,7 +390,7 @@ Some of our standard security queries use flow labels. You can look at their imp
390390
to get a feeling for how to use flow labels in practice.
391391

392392
In particular, both of the examples mentioned in the section on limitations of basic data flow above
393-
are from standard security queries that use flow labels. The `Prototype-pollutiing merge call
393+
are from standard security queries that use flow labels. The `Prototype-polluting merge call
394394
<https://codeql.github.com/codeql-query-help/javascript/js-prototype-pollution/>`_ query uses two flow labels to distinguish completely
395395
tainted objects from partially tainted objects. The `Uncontrolled data used in path expression
396396
<https://codeql.github.com/codeql-query-help/javascript/js-path-injection/>`_ query uses four flow labels to track whether a user-controlled

0 commit comments

Comments
 (0)