-
Notifications
You must be signed in to change notification settings - Fork 1
fix(deps): update dependency sharp to v0.32.6 [security] #323
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
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
59c545c to
3de0926
Compare
3de0926 to
81d699b
Compare
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: pnpm-lock.yaml |
|
This PR contains the following updates:
0.29.0->0.32.6GitHub Vulnerability Alerts
CVE-2022-29256
There's a possible vulnerability in logic that is run only at
npm installtime when installing versions ofsharpprior to the latest v0.30.5.This is not part of any runtime code, does not affect Windows users at all, and is unlikely to affect anyone that already cares about the security of their build environment. However, out of an abundance of caution, I've created this advisory.
If an attacker has the ability to set the value of the
PKG_CONFIG_PATHenvironment variable in a build environment then they might be able to use this to inject an arbitrary command atnpm installtime.I've used the Common Vulnerability Scoring System (CVSS) calculator to determine the maximum possible impact, which suggests a "medium" score of 5.9, but for most people the real impact will be dealing with the noise from automated security tooling that this advisory will bring.
AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C/CR:X/IR:X/AR:X/MAV:X/MAC:X/MPR:X/MUI:R/MS:X/MC:X/MI:X/MA:XThis problem was fixed in commit a6aeef6 and published as part of
sharpv0.30.5.Thank you very much to @dwisiswant0 for the responsible disclosure.
Remember: if an attacker has control over environment variables in your build environment then you have a bigger problem to deal with than this issue.
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.6Compare Source
v0.32.5Compare Source
v0.32.4Compare Source
v0.32.3Compare Source
v0.32.2Compare Source
v0.32.1Compare Source
v0.32.0Compare Source
v0.31.3Compare Source
v0.31.2Compare Source
v0.31.1Compare Source
v0.31.0Compare Source
v0.30.7Compare Source
v0.30.6Compare Source
v0.30.5Compare Source
v0.30.4Compare Source
v0.30.3Compare Source
v0.30.2Compare Source
v0.30.1Compare Source
v0.30.0Compare Source
v0.29.3Compare Source
v0.29.2Compare Source
v0.29.1Compare Source
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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.