forked from juice-shop/juice-shop
-
Notifications
You must be signed in to change notification settings - Fork 8
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
[ Lab ] Testing remediations after retry improvements #101
Closed
Closed
Changes from 1 commit
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
f3248e7
Added search query + introduced vulnerability
mwillfox b0ada84
Amplify Security - Code fix for CWE-89 accepted
amplify-local[bot] 4a425aa
Revert "Amplify Security - Code fix for CWE-89 accepted"
mwillfox 1d3a90a
Amplify Security - Code fix for CWE-89 accepted
amplify-local[bot] f827337
Revert "Amplify Security - Code fix for CWE-89 accepted"
mwillfox 6a67766
Amplify Security - Code fix for CWE-89 accepted
amplify-local[bot] c457624
Revert "Amplify Security - Code fix for CWE-89 accepted"
mwillfox 6f8b7a8
Amplify Security - Code fix for CWE-89 accepted
amplify-local[bot] 85f1b51
Revert "Amplify Security - Code fix for CWE-89 accepted"
mwillfox f05622b
Amplify Security - Code fix for CWE-89 accepted
amplify-local[bot] 7fd60f2
Revert "Amplify Security - Code fix for CWE-89 accepted"
mwillfox File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next
Next commit
Added search query + introduced vulnerability
- Loading branch information
commit f3248e70d60dc1eab4c98ba3e63a688a199d681a
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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.
Warning
Amplify has been notified that this line contains a vulnerability 🕷️.
Vulnerability: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Impact: HIGH
Guidance: ✅
Code Fix: ✅
Learn more about this alert
The code change fixes the SQL Injection vulnerability by using parameterized queries instead of directly concatenating user input into the SQL query.
In the original code, the user input
criteria
is directly interpolated into the SQL query using string concatenation. This allows an attacker to manipulate the input and inject malicious SQL code, potentially leading to unauthorized access or data manipulation.In the fixed code, the
criteria
value is passed as a parameter using thereplacements
option in thesequelize.query
method. This ensures that the user input is properly escaped and treated as a parameter rather than part of the SQL query itself. Parameterized queries help prevent SQL Injection attacks by separating the SQL code from the user input.By using parameterized queries, the fixed code mitigates the SQL Injection vulnerability and makes the application more secure.
For more information on SQL Injection and how to prevent it, you can refer to the OWASP SQL Injection Prevention Cheat Sheet: OWASP SQL Injection Prevention Cheat Sheet
Note
Have a question or concern about this vulnerability fix? Get an answer within seconds by asking our Concierge 🤖 with
@amplify-security
.i.e. @amplify-security are there known performance issues resulting from this fix?