Update dependency sharp to ^0.30.0 [SECURITY] #60
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.22.0
->^0.30.0
GitHub Vulnerability Alerts
CVE-2022-29256
There's a possible vulnerability in logic that is run only at
npm install
time when installing versions ofsharp
prior 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_PATH
environment variable in a build environment then they might be able to use this to inject an arbitrary command atnpm install
time.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:X
This problem was fixed in commit a6aeef6 and published as part of
sharp
v0.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.
Release Notes
lovell/sharp (sharp)
v0.30.5
Compare Source
v0.30.4
Compare Source
v0.30.3
Compare Source
v0.30.2
Compare Source
v0.30.1
Compare Source
v0.30.0
Compare Source
v0.29.3
Compare Source
v0.29.2
Compare Source
v0.29.1
Compare Source
v0.29.0
Compare Source
v0.28.3
Compare Source
v0.28.2
Compare Source
v0.28.1
Compare Source
v0.28.0
Compare Source
v0.27.2
Compare Source
v0.27.1
Compare Source
v0.27.0
Compare Source
v0.26.3
Compare Source
v0.26.2
Compare Source
v0.26.1
Compare Source
v0.26.0
Compare Source
v0.25.4
Compare Source
v0.25.3
Compare Source
v0.25.2
Compare Source
v0.25.1
Compare Source
v0.25.0
Compare Source
v0.24.1
Compare Source
v0.24.0
Compare Source
v0.23.4
Compare Source
v0.23.3
Compare Source
v0.23.2
Compare Source
v0.23.1
Compare Source
v0.23.0
Compare Source
v0.22.1
Compare 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.