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
feat(torii-grpc): ordering and pagination #2765
feat(torii-grpc): ordering and pagination #2765
Changes from 3 commits
e2b5598
eba095d
424a166
b605642
7a7363d
2827f71
5769af2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Potential SQL Injection Vulnerability: Validate
where_clause
ParameterOhayo sensei! Passing the
where_clause
parameter directly into SQL query strings without proper sanitization can lead to SQL injection vulnerabilities. Please ensure thatwhere_clause
is properly validated or use parameterized queries to prevent SQL injection attacks.Apply this diff to use parameterized queries:
Also applies to: 298-302
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.
Potential SQL Injection Vulnerability: Validate Input Parameters
Ohayo sensei! Passing user-provided
where_clause
,order_by
,updated_before
, andupdated_after
parameters directly into SQL queries can lead to SQL injection vulnerabilities. Please ensure that these parameters are properly sanitized or use parameterized queries.Consider modifying the code to use parameterized queries for these parameters and validate their values before incorporating them into SQL statements.
Also applies to: 475-477
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.
Potential SQL Injection Risk in
retrieve_entities
MethodOhayo sensei! The
order_by
parameter is constructed using string formatting and injected directly into the SQL query, which can introduce SQL injection vulnerabilities. Please validate theorder_by
parameter against a whitelist of allowed values or use parameterized queries to prevent SQL injection attacks.Consider the following refactor to validate
order_by
:Implement a helper function
is_valid_identifier
to ensure that only allowed column names are used.