-
Notifications
You must be signed in to change notification settings - Fork 1
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 grunt to v1.5.3 [security] #25
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/npm-grunt-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
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
changed the title
chore(deps): update dependency grunt to v1.3.0 [security]
chore(deps): update dependency grunt to v1.5.2 [security]
May 16, 2022
renovate
bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
June 18, 2022 18:49
7057251
to
d82329e
Compare
renovate
bot
changed the title
chore(deps): update dependency grunt to v1.5.2 [security]
chore(deps): update dependency grunt to v1.5.3 [security]
Jun 18, 2022
renovate
bot
changed the title
chore(deps): update dependency grunt to v1.5.3 [security]
chore(deps): update dependency grunt to v1.5.3 [security] - autoclosed
Jul 17, 2023
renovate
bot
changed the title
chore(deps): update dependency grunt to v1.5.3 [security] - autoclosed
chore(deps): update dependency grunt to v1.5.3 [security]
Jul 17, 2023
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.3
GitHub 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.3
Compare Source
572d79b
58016ff
0749e1d
69b7c50
v1.5.2
Compare Source
7f15fd5
b0ec6e1
433f91b
v1.5.1
Compare Source
ad22608
0652305
v1.5.0
Compare Source
b2b2c2b
3eda6ae
47d32de
2e9161c
04b960e
aad3d45
fdc7056
e35fe54
v1.4.1
Compare Source
e7625e5
5d67e34
d13bf88
08896ae
eee0673
1b6e288
v1.4.0
Compare Source
63b2e89
106ed17
49de70b
47cf8b6
e86db1c
4952368
v1.3.0
Compare Source
faab6be
520fedb
7e669ac
safeLoad
for loading YML files viafile.readYAML
.e350cea
7125f49
00d5907
v1.2.1
Compare Source
ae11839
9d23cb6
e789b1f
v1.2.0
Compare 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.0
Compare Source
v1.0.4
Compare Source
v1.0.3
Compare Source
v1.0.2
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 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.