Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Rust: Value flow and taint flow through formatting strings #18394
Rust: Value flow and taint flow through formatting strings #18394
Changes from 5 commits
f09632d
42d1256
2ef9339
0d19fb6
cd957ba
5c64a8c
c55b256
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Check warning on line 189 in rust/ql/lib/codeql/rust/controlflow/CfgNodes.qll
GitHub Actions / qldoc
Check warning on line 193 in rust/ql/lib/codeql/rust/controlflow/CfgNodes.qll
GitHub Actions / qldoc
Check warning on line 202 in rust/ql/lib/codeql/rust/controlflow/CfgNodes.qll
GitHub Actions / qldoc
Check warning on line 207 in rust/ql/lib/codeql/rust/controlflow/CfgNodes.qll
GitHub Actions / qldoc
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this rather be
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Conceptually yes, but
MacroCall
is not an expression and doesn't have a node in the data-flow graph, so it won't work. To do that I think we'd have to change the type ofgetALastEvalNode
and add a new kind of data-flow node forMacroCall
.ThaSo just adding a step over the
MacroCall
seems simpler and is also what we do for the other kind of nodes that have their expression nested further down.We could add a method on
MacroExprCfgNode
to get the expanded node directly?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, let's leave it as-is then.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.