Fix: SQL Injection in Database Migration #351
Open
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.
🔧 Fix Implementation
This PR addresses the critical SQL injection vulnerability identified in issue #346.
Changes Made
Security Improvements
Files Modified
Code Changes
Before (Vulnerable)
ypescript // VULNERABLE CODE await queryRunner.query( UPDATE app_connection SET value = '' WHERE id = );After (Fixed)
ypescript // FIXED CODE - Use parameterized queries await queryRunner.query( 'UPDATE app_connection SET value = WHERE id = ', [JSON.stringify(currentConnection.value), currentConnection.id] );Impact
Researcher: grich88 (j.grant.richards@proton.me)
Closes #346