Skip to content
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

Update dependency sharp to v0.30.5 [SECURITY] #497

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jun 1, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
sharp (changelog) 0.28.3 -> 0.30.5 age adoption passing confidence

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

GitHub Vulnerability Alerts

CVE-2022-29256

There's a possible vulnerability in logic that is run only at npm install time when installing versions of sharp 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 at npm 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

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


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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/npm-sharp-vulnerability branch 6 times, most recently from 9221c08 to d7e6bc7 Compare June 12, 2022 12:25
@renovate renovate bot force-pushed the renovate/npm-sharp-vulnerability branch from d7e6bc7 to 698251b Compare September 25, 2022 22:28
@renovate renovate bot force-pushed the renovate/npm-sharp-vulnerability branch from 698251b to 056a102 Compare November 20, 2022 07:37
@renovate renovate bot force-pushed the renovate/npm-sharp-vulnerability branch from 056a102 to d3ce1a2 Compare March 17, 2023 01:47
@renovate renovate bot changed the title Update dependency sharp to 0.30.5 [SECURITY] Update dependency sharp to v0.30.5 [SECURITY] Mar 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants