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
PS-3323: Adding New Fields from the backend #131
PS-3323: Adding New Fields from the backend #131
Changes from 5 commits
e512b83
2bb4709
d8a04e7
38bf4f9
ea303be
3177f36
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.
💡 Codebase verification
SQL injection vulnerabilities confirmed and expanded
String interpolation in SQL queries is present across multiple files, creating security vulnerabilities:
src/adapters/postgres/user-adapter.ts
: Multiple instances in WHERE conditions using ILIKE and direct value injectionsrc/adapters/postgres/fields-adapter.ts
: Direct value injection in field queriessrc/adapters/postgres/cohortMembers-adapter.ts
: ILIKE condition with string interpolationConsider using parameterized queries consistently across all database adapters to prevent SQL injection attacks.
🔗 Analysis chain
Reconsider SQL injection prevention
While marked as "not required" in past reviews, using string interpolation for SQL queries remains a security risk. Consider using parameterized queries to prevent potential SQL injection attacks.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
Length of output: 45
Script:
Length of output: 640
Script:
Length of output: 2584
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.
💡 Codebase verification
Email should not be set to null in Keycloak user creation
The codebase shows that email is a critical field used for user identification, password reset, and notifications. Setting it to null could break:
Consider:
@IsEmail()
) from UserDtoemail: query.email ? query.email : null
🔗 Analysis chain
Verify email handling in Keycloak integration.
Setting email to null might cause issues with Keycloak's user management. Consider:
Also, the commented-out groups assignment
// groups: [getUserGroup(query.role)]
suggests incomplete role management.🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
Length of output: 35
Script:
Length of output: 22430