🚨 [security] Update json 2.10.1 → 2.10.2 (patch) #42
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.
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
Security Advisories 🚨
🚨 Out-of-bounds Read in Ruby JSON Parser
Commits
See the full diff on Github. The new version differs by 12 commits:
Release 2.10.2
Merge commit from fork
Fix potential out of bound read in `json_string_unescape`.
Merge pull request #762 from byroot/invalid-escape
Raise a ParserError on all incomplete unicode escape sequence.
Avoid fast-path IO writes when IO has ext enc
Merge pull request #757 from rahim/fix-generator-error-no-method-error
Fix JSON::GeneratorError#detailed_message with Ruby < 3.2
Merge pull request #756 from byroot/utf8-snippets
Ensure parser error snippets are valid UTF-8
Merge pull request #753 from ioquatix/json-dump-options
Pass through all options if present.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands