zync
zync copied to clipboard
🚨 [security] Update yajl-ruby: 1.4.1 → 1.4.2 (patch)
🚨 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?
↗️ yajl-ruby (indirect, 1.4.1 → 1.4.2) · Repo · Changelog
Security Advisories 🚨
🚨 Reallocation bug can trigger heap memory corruption
The 1.x branch and the 2.x branch of yajl
contain an integer overflow which leads to subsequent heap memory corruption
when dealing with large (~2GB) inputs.Details
The reallocation logic at yajl_buf.c#L64
may result in theneed
32bit integer wrapping to 0 whenneed
approaches
a value of 0x80000000 (i.e. ~2GB of data), which results in a reallocation
of buf->alloc into a small heap chunk.These integers are declared as
size_t
in the 2.x branch ofyajl
, which
practically prevents the issue from triggering on 64bit platforms, however
this does not preclude this issue triggering on 32bit builds on which
size_t
is a 32bit integer.Subsequent population of this under-allocated heap chunk is based on the
original buffer size, leading to heap memory corruption.Impact
We rate this as a moderate severity vulnerability which mostly impacts
process availability as we believe exploitation for arbitrary code
execution to be unlikely.Patches
Patched in yajl-ruby 1.4.2
Workarounds
Avoid passing large inputs to YAJL
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
- @depfu rebase
- Rebases against your default branch and redoes this update
- @depfu recreate
- Recreates this PR, overwriting any edits that you've made to it
- @depfu merge
- Merges this PR once your tests are passing and conflicts are resolved
- @depfu close
- Closes this PR and deletes the branch
- @depfu reopen
- Restores the branch and reopens this PR (if it's closed)
- @depfu pause
- Ignores all future updates for this dependency and closes this PR
- @depfu pause [minor|major]
- Ignores all future minor/major updates for this dependency and closes this PR
- @depfu resume
- Future versions of this dependency will create PRs again (leaves this PR as is)