This repository was archived by the owner on Jan 15, 2025. It is now read-only.
chore(deps): update dependency grunt to v1.5.3 [security] - #25
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
May 13, 2021 15:16
ab99759 to
ef28acc
Compare
renovate
Bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
March 7, 2022 08:47
ef28acc to
4ed30c9
Compare
renovate
Bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
March 26, 2022 13:18
4ed30c9 to
a74b4c1
Compare
renovate
Bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
April 24, 2022 18:59
a74b4c1 to
7057251
Compare
renovate
Bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
June 18, 2022 18:49
7057251 to
d82329e
Compare
renovate
Bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
July 17, 2023 03:43
d82329e to
d2baa91
Compare
renovate
Bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
August 9, 2023 12:08
d2baa91 to
8a6269f
Compare
renovate
Bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
September 19, 2023 14:12
8a6269f to
d6aa055
Compare
renovate
Bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
2 times, most recently
from
October 15, 2023 17:06
5fcd9a3 to
c375882
Compare
renovate
Bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
October 23, 2023 13:36
c375882 to
3a6cabb
Compare
renovate
Bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
November 6, 2023 08:26
3a6cabb to
2e02b69
Compare
renovate
Bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
February 25, 2024 09:06
2e02b69 to
71f0dd4
Compare
renovate
Bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
March 12, 2024 11:57
71f0dd4 to
fd52878
Compare
renovate
Bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
June 4, 2024 14:36
fd52878 to
d3a61d8
Compare
renovate
Bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
July 21, 2024 15:03
d3a61d8 to
2bc9280
Compare
renovate
Bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
August 28, 2024 07:56
2bc9280 to
f49ac5c
Compare
renovate
Bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
December 8, 2024 23:12
b4699bb to
f49ac5c
Compare
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
1.0.1->1.5.3GitHub Vulnerability Alerts
CVE-2020-7729
The package grunt before 1.3.0 are vulnerable to Arbitrary Code Execution due to the default usage of the function load() instead of its secure replacement safeLoad() of the package js-yaml inside grunt.file.readYAML.
CVE-2022-0436
Grunt prior to version 1.5.2 is vulnerable to path traversal.
CVE-2022-1537
file.copy operations in GruntJS are vulnerable to a TOCTOU race condition leading to arbitrary file write in GitHub repository gruntjs/grunt prior to 1.5.3. This vulnerability is capable of arbitrary file writes which can lead to local privilege escalation to the GruntJS user if a lower-privileged user has write access to both source and destination directories as the lower-privileged user can create a symlink to the GruntJS user's .bashrc file or replace /etc/shadow file if the GruntJS user is root.
Release Notes
gruntjs/grunt (grunt)
v1.5.3Compare Source
572d79b58016ff0749e1d69b7c50v1.5.2Compare Source
7f15fd5b0ec6e1433f91bv1.5.1Compare Source
ad226080652305v1.5.0Compare Source
b2b2c2b3eda6ae47d32de2e9161c04b960eaad3d45fdc7056e35fe54v1.4.1Compare Source
e7625e55d67e34d13bf8808896aeeee06731b6e288v1.4.0Compare Source
63b2e89106ed1749de70b47cf8b6e86db1c4952368v1.3.0Compare Source
faab6be520fedb7e669acsafeLoadfor loading YML files viafile.readYAML.e350cea7125f4900d5907v1.2.1Compare Source
ae118399d23cb6e789b1fv1.2.0Compare Source
is visible to Node.js and NPM, instead of node_modules directly
inside package that have a dev dependency to these pluginhttps://github.com/gruntjs/grunt/pull/1677nt/pull/1677)
coffeescript is still around, Grunt will attempt to load it.
If it is not, and the user loads a CoffeeScript file,
Grunt will print a useful error indicating that the
coffeescript package should be installed as a dev dependency.
This is considerably more user-friendly than dropping the require entirely,
but doing so is feasible with the latest grunt-cli as users
may simply use grunt --require https://github.com/gruntjs/grunt/pull/1675thub.com/Remove coffeescript from dependencies. gruntjs/grunt#1675)
(https://github.com/gruntjs/grunt/pull/15701570)
(https://github.com/gruntjs/grunt/pull/16971697)
v1.1.0Compare Source
v1.0.4Compare Source
v1.0.3Compare Source
v1.0.2Compare 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 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.