-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update dependency sharp to v0.32.6 [security] #1238
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/npm-sharp-vulnerability
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
Deploying daim with Cloudflare Pages
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
renovate
bot
force-pushed
the
renovate/npm-sharp-vulnerability
branch
from
December 7, 2023 07:41
26b056f
to
8bf4033
Compare
renovate
bot
force-pushed
the
renovate/npm-sharp-vulnerability
branch
from
December 7, 2023 11:13
8bf4033
to
70bc2b1
Compare
renovate
bot
force-pushed
the
renovate/npm-sharp-vulnerability
branch
from
December 7, 2023 13:39
70bc2b1
to
d05bf7e
Compare
renovate
bot
force-pushed
the
renovate/npm-sharp-vulnerability
branch
from
December 9, 2023 05:21
d05bf7e
to
a8c1dc8
Compare
renovate
bot
force-pushed
the
renovate/npm-sharp-vulnerability
branch
from
December 11, 2023 07:40
a8c1dc8
to
c9daee7
Compare
renovate
bot
force-pushed
the
renovate/npm-sharp-vulnerability
branch
from
December 13, 2023 03:50
c9daee7
to
6402870
Compare
renovate
bot
force-pushed
the
renovate/npm-sharp-vulnerability
branch
from
January 16, 2024 00:52
6402870
to
29a0d05
Compare
renovate
bot
force-pushed
the
renovate/npm-sharp-vulnerability
branch
from
January 23, 2024 00:15
29a0d05
to
162d330
Compare
renovate
bot
force-pushed
the
renovate/npm-sharp-vulnerability
branch
from
January 23, 2024 01:00
162d330
to
f810013
Compare
renovate
bot
force-pushed
the
renovate/npm-sharp-vulnerability
branch
from
January 23, 2024 05:06
f810013
to
ea41a64
Compare
renovate
bot
force-pushed
the
renovate/npm-sharp-vulnerability
branch
from
January 25, 2024 01:24
ea41a64
to
7274c79
Compare
renovate
bot
changed the title
chore(deps): update dependency sharp to v0.32.6 [security]
chore(deps): update dependency sharp to v0.32.6 [security] - autoclosed
Feb 24, 2024
renovate
bot
changed the title
chore(deps): update dependency sharp to v0.32.6 [security] - autoclosed
chore(deps): update dependency sharp to v0.32.6 [security]
Feb 24, 2024
renovate
bot
force-pushed
the
renovate/npm-sharp-vulnerability
branch
from
February 24, 2024 05:34
7274c79
to
1e79bf4
Compare
renovate
bot
force-pushed
the
renovate/npm-sharp-vulnerability
branch
from
March 28, 2024 04:53
1e79bf4
to
7e26aaf
Compare
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 contains the following updates:
0.32.0
->0.32.6
GitHub Vulnerability Alerts
GHSA-54xq-cgqr-rpm3
Overview
sharp uses libwebp to decode WebP images and versions prior to the latest 0.32.6 are vulnerable to the high severity GHSA-j7hp-h8jx-5ppr.
Who does this affect?
Almost anyone processing untrusted input with versions of sharp prior to 0.32.6.
How to resolve this?
Using prebuilt binaries provided by sharp?
Most people rely on the prebuilt binaries provided by sharp.
Please upgrade sharp to the latest 0.32.6, which provides libwebp 1.3.2.
Using a globally-installed libvips?
Please ensure you are using the latest libwebp 1.3.2.
Possible workaround
Add the following to your code to prevent sharp from decoding WebP images.
Release Notes
lovell/sharp (sharp)
v0.32.6
Compare Source
v0.32.5
Compare Source
v0.32.4
Compare Source
v0.32.3
Compare Source
v0.32.2
Compare Source
v0.32.1
Compare Source
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.