Updating the json-path and json smaprt version, to fix the security v…#121
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Overview
This pull request addresses a reported security vulnerability (CVE-2024-57699) in the json-smart dependency. The following changes have been made to ensure the project remains secure and up-to-date:
Key Changes
Updated json-smart Dependency: Upgraded to version 2.6.0 to resolve the CVE-2024-57699 security issue.
Updated json-path Dependency: Upgraded to the latest version to fix transitive dependency issues related to json-smart.
Impact
These updates mitigate known security risks and improve overall dependency hygiene. No changes were made to application logic or functionality.