Blind sql injection vulnerabilities secure implementations #477
Conversation
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
imertetsu
changed the title
|
Hi @preetkaran20, sorry, I created a PR with previous commits that I made, so I closed it, I created this new PR with only the commits that should be :) |
preetkaran20
approved these changes
Nov 11, 2024
|
@imertetsu Thanks a lot for the PR. It LGTM and hence merging the PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds Blind SQL injection secure implementations for levels 4 and 5 in the BlindSQLInjectionVulnerability class.
Level 4: Implementation of getCarInformationLevel4 method using parameterized queries with JdbcTemplate.
Level 5: Implementation of the getCarInformationLevel5 method using EntityManager to safely perform queries using Hibernate, avoiding SQL injection.
Resolves: #405