Update vulnerable packages to resolve security issues #278
Conversation
This file contains hidden or 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
prachi-okta
previously approved these changes
Apr 1, 2025
prachi-okta
approved these changes
Apr 4, 2025
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.
Description
Fixes the issue #269 with outdated package dependencies causing security vulnerabilities.
Why is this change necessary?
The outdated versions of these packages contain known security vulnerabilities that could be exploited, leading to potential breaches. Updating these dependencies ensures compliance with security policies and improves the overall security posture of the project.
Testing
Verified the updated package versions using dotnet list package --include-transitive.
Ran security scanning tools (dotnet retire) to confirm that the vulnerabilities are resolved.
Built and tested the solution to ensure no breaking changes were introduced.
Triggered the snyk scan to verify no vulnerable component found