-
-
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 [security] #52
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 }}
Could not load tags
Nothing to show
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 15, 2021 19:33
cff2316
to
a02310d
Compare
renovate
bot
changed the title
chore(deps): pin dependency grunt to 0.4.5 [security]
chore(deps): update dependency grunt to v1 [security]
May 15, 2021
renovate
bot
changed the title
chore(deps): update dependency grunt to v1 [security]
chore(deps): pin dependency grunt to v0.4.5 [security]
Jun 6, 2021
renovate
bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
June 6, 2021 21:47
a02310d
to
e751028
Compare
renovate
bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
February 14, 2022 00:52
e751028
to
23f9f5a
Compare
renovate
bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
February 14, 2022 04:17
23f9f5a
to
043e3e4
Compare
renovate
bot
changed the title
chore(deps): pin dependency grunt to v0.4.5 [security]
chore(deps): update dependency grunt to v1 [security]
Feb 14, 2022
renovate
bot
changed the title
chore(deps): update dependency grunt to v1 [security]
chore(deps): pin dependency grunt to v0.4.5 [security]
Feb 15, 2022
renovate
bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
2 times, most recently
from
February 15, 2022 14:51
9596298
to
fad519e
Compare
renovate
bot
changed the title
chore(deps): pin dependency grunt to v0.4.5 [security]
chore(deps): update dependency grunt to v1 [security]
Feb 15, 2022
renovate
bot
changed the title
chore(deps): update dependency grunt to v1 [security]
chore(deps): pin dependency grunt to v0.4.5 [security]
Feb 16, 2022
renovate
bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
2 times, most recently
from
February 16, 2022 12:50
a9530eb
to
7a70a0e
Compare
renovate
bot
changed the title
chore(deps): pin dependency grunt to v0.4.5 [security]
chore(deps): update dependency grunt to v1 [security]
Feb 16, 2022
renovate
bot
changed the title
chore(deps): update dependency grunt to v1 [security]
chore(deps): pin dependency grunt to v0.4.5 [security]
Feb 17, 2022
renovate
bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
2 times, most recently
from
February 17, 2022 12:48
40e37a4
to
f2ec296
Compare
renovate
bot
changed the title
chore(deps): pin dependency grunt to v0.4.5 [security]
chore(deps): update dependency grunt to v1 [security]
Feb 17, 2022
renovate
bot
changed the title
chore(deps): update dependency grunt to v1 [security]
chore(deps): pin dependency grunt to v0.4.5 [security]
Feb 18, 2022
renovate
bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
2 times, most recently
from
February 18, 2022 14:43
53d5943
to
77ccfc9
Compare
renovate
bot
changed the title
chore(deps): pin dependency grunt to v0.4.5 [security]
chore(deps): update dependency grunt to v1 [security]
Feb 18, 2022
renovate
bot
changed the title
chore(deps): update dependency grunt to v1 [security]
chore(deps): pin dependency grunt to v0.4.5 [security]
Feb 23, 2022
renovate
bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
February 23, 2022 14:47
77ccfc9
to
1bf5ad0
Compare
renovate
bot
changed the title
chore(deps): pin dependency grunt to v0.4.5 [security]
chore(deps): update dependency grunt to v1 [security]
Feb 23, 2022
renovate
bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
February 23, 2022 17:02
1bf5ad0
to
c8ebea0
Compare
renovate
bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
February 6, 2024 04:58
599f2d2
to
36aeef1
Compare
renovate
bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
2 times, most recently
from
February 19, 2024 02:49
6479623
to
4c0b743
Compare
renovate
bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
4 times, most recently
from
March 2, 2024 05:14
3194ac1
to
c727733
Compare
renovate
bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
4 times, most recently
from
March 16, 2024 05:45
f6e7472
to
68342dc
Compare
renovate
bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
3 times, most recently
from
March 25, 2024 02:48
7288d96
to
878b6ce
Compare
renovate
bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
March 29, 2024 02:41
878b6ce
to
cd692b3
Compare
renovate
bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
2 times, most recently
from
April 16, 2024 23:38
82f63b7
to
e56c9bc
Compare
renovate
bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
4 times, most recently
from
April 27, 2024 08:43
b01dc12
to
2061c8c
Compare
renovate
bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
3 times, most recently
from
May 9, 2024 08:56
4ccd2d0
to
095a1a8
Compare
renovate
bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
May 10, 2024 23:43
095a1a8
to
89ba940
Compare
renovate
bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
2 times, most recently
from
May 25, 2024 05:30
61fa2bb
to
dc1d1f6
Compare
renovate
bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
June 5, 2024 05:26
dc1d1f6
to
5d3d624
Compare
renovate
bot
force-pushed
the
renovate/npm-grunt-vulnerability
branch
from
June 6, 2024 05:58
5d3d624
to
cb27317
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.4.0
->~1.5.3
~0.4.5
->~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
v1.0.1
Compare Source
v1.0.0
Compare Source
v0.4.5
Compare Source
v0.4.4
Compare Source
v0.4.3
Compare Source
v0.4.2
Compare Source
v0.4.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 these updates again.
This PR has been generated by Mend Renovate. View repository job log here.