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 grunt [SECURITY] #32

Merged
merged 1 commit into from
May 31, 2024
Merged

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented May 31, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
grunt (source) ~0.4.1 -> ~1.5.0 age adoption passing confidence
grunt (source) ~0.3.17 -> ~0.4.0 age adoption passing confidence
grunt (source) ~0.4.5 -> ~1.6.0 age adoption passing confidence
grunt (source) ~0.4.1 -> ~1.6.0 age adoption passing confidence
grunt (source) ~0.4.2 -> ~1.6.0 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

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

v1.5.2

Compare Source

v1.5.1

Compare Source

v1.5.0

Compare Source

v1.4.1

Compare Source

v1.4.0

Compare Source

v1.3.0

Compare Source

  • Merge pull request #​1720 from gruntjs/update-changelog-deps faab6be
  • Update Changelog and legacy-util dependency 520fedb
  • Merge pull request #​1719 from gruntjs/yaml-refactor 7e669ac
  • Switch to use safeLoad for loading YML files via file.readYAML. e350cea
  • Merge pull request #​1718 from gruntjs/legacy-log-bumo 7125f49
  • Bump legacy-log 00d5907

v1.2.1

Compare Source

v1.2.0

Compare Source

v1.1.0

Compare Source

  • Update to mkdirp ~1.0.3
  • Only support versions of Node >= 8

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


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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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-grunt-vulnerability branch from 0814409 to 707af74 Compare May 31, 2024 09:43
@renovate renovate bot changed the title Update dependency grunt [SECURITY] Update dependency grunt to v1 [SECURITY] May 31, 2024
@renovate renovate bot force-pushed the renovate/npm-grunt-vulnerability branch from 707af74 to b757343 Compare May 31, 2024 09:50
@renovate renovate bot changed the title Update dependency grunt to v1 [SECURITY] Update dependency grunt [SECURITY] May 31, 2024
Copy link
Author

renovate bot commented May 31, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: community/browser/npm-shrinkwrap.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: grunt-bower-requirejs@0.4.4
npm error Found: grunt@1.5.3
npm error node_modules/grunt
npm error   dev grunt@"~1.5.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer grunt@"~0.4.0" from grunt-bower-requirejs@0.4.4
npm error node_modules/grunt-bower-requirejs
npm error   dev grunt-bower-requirejs@"~0.4.1" from the root project
npm error
npm error Conflicting peer dependency: grunt@0.4.5
npm error node_modules/grunt
npm error   peer grunt@"~0.4.0" from grunt-bower-requirejs@0.4.4
npm error   node_modules/grunt-bower-requirejs
npm error     dev grunt-bower-requirejs@"~0.4.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-05-31T09_50_35_397Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-31T09_50_35_397Z-debug-0.log

@sarvex sarvex merged commit d93a54a into 2.3 May 31, 2024
1 of 2 checks passed
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.

1 participant