Bump micromatch from 4.0.7 to 4.0.8 #2
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=80&v=4){kind=small}
Bumps [micromatch](https://github.com/micromatch/micromatch) from 4.0.7 to 4.0.8. - [Release notes](https://github.com/micromatch/micromatch/releases) - [Changelog](https://github.com/micromatch/micromatch/blob/master/CHANGELOG.md) - [Commits](micromatch/micromatch@4.0.7...4.0.8) --- updated-dependencies: - dependency-name: micromatch dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
the
dependencies
Reviewer's Guide by SourceryThis pull request updates the micromatch dependency from version 4.0.7 to 4.0.8. The update includes fixes for two CVE vulnerabilities (CVE-2024-4067 and CVE-2024-4068), which are considered low-priority by the package maintainers. The changes primarily affect the pnpm-lock.yaml file with dependency resolution updates. No diagrams generated as the changes look simple and do not need a visual representation. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
![codacy-production[bot]](https://avatars.githubusercontent.com/in/56611?s=60&v=4){kind=small}
| resolution: {integrity: sha512-Xa4Nw17FS9ApQFJ9umLiJS4orGjm7ZzwUrwamcGQuHSzDyth9boKDaycYdDcZDuqYATXw4HFXgaqWTctW/v1HA==} | ||
| engines: {node: '>=16 || 14 >=14.18'} | ||
|
|
||
| path-to-regexp@6.2.2: |
There was a problem hiding this comment.
❌ Codacy found a critical Security issue: Insecure dependency path-to-regexp@6.2.2 (CVE-2024-45296: path-to-regexp: Backtracking regular expressions cause ReDoS) (update to 6.3.0)
The issue identified by the Trivy linter is related to a security vulnerability in the path-to-regexp package version 6.2.2. This vulnerability is a Regular Expression Denial of Service (ReDoS) issue, which occurs when an attacker can exploit a poorly constructed regular expression to cause excessive backtracking. This can lead to significant performance degradation or even service unavailability, as the regular expression engine gets stuck trying to evaluate complex patterns.
The recommended fix is to update the path-to-regexp package to version 6.3.0, which contains patches to address this vulnerability.
Here's the code suggestion to fix the issue by updating the package version:
| path-to-regexp@6.2.2: | |
| path-to-regexp@6.3.0: |
This comment was generated by an experimental AI tool.
| resolution: {integrity: sha512-+1VkjdD0QBLPodGrJUeqarH8VAIvQODIbwh9XpP5Syisf7YoQgsJKPNFoqqLQlu+VQ/tVSshMR6loPMn8U+dPg==} | ||
| engines: {node: '>=14'} | ||
|
|
||
| '@rollup/rollup-android-arm-eabi@4.18.0': |
There was a problem hiding this comment.
❌ Codacy found a critical Security issue: Insecure dependency rollup@4.18.0 (CVE-2024-47068: rollup: DOM Clobbering Gadget found in rollup bundled scripts that leads to XSS) (update to 4.22.4)
The issue identified by the Trivy linter is a security vulnerability in the version 4.18.0 of the rollup package. The vulnerability, identified as CVE-2024-47068, is related to a DOM Clobbering Gadget found in scripts bundled by rollup. This vulnerability could potentially lead to Cross-Site Scripting (XSS) attacks, which can allow attackers to execute arbitrary scripts in the context of a user's browser session.
To address this issue, it is recommended to update the rollup package to a version where the vulnerability is patched. According to the issue description, the fixed version is 4.22.4.
Here's the code suggestion to fix the issue by updating the rollup package version:
| '@rollup/rollup-android-arm-eabi@4.18.0': | |
| '@rollup/rollup-android-arm-eabi@4.22.4': |
This comment was generated by an experimental AI tool.
| '@types/cheerio@0.22.35': | ||
| resolution: {integrity: sha512-yD57BchKRvTV+JD53UZ6PD8KWY5g5rvvMLRnZR3EQBCZXiDT/HR+pKpMzFGlWNhFrXlo7VPZXtKvIEwZkAWOIA==} | ||
|
|
||
| '@types/cookie@0.6.0': |
There was a problem hiding this comment.
ℹ️ Codacy found a minor Security issue: Insecure dependency cookie@0.6.0 (CVE-2024-47764: cookie: cookie accepts cookie name, path, and domain with out of bounds characters) (update to 0.7.0)
The issue identified by Trivy is related to a security vulnerability in the cookie package version 0.6.0. The vulnerability, identified as CVE-2024-47764, involves the cookie library accepting cookie names, paths, and domains with characters that are out of bounds. This can potentially lead to security risks such as improper handling of cookies, which may be exploited by malicious actors. The recommended solution is to update the cookie package to version 0.7.0, where this vulnerability is addressed.
To fix this issue, the version of the cookie package should be updated to 0.7.0. Here is the code suggestion to address the issue:
| '@types/cookie@0.6.0': | |
| '@types/cookie@0.7.0': |
This comment was generated by an experimental AI tool.
| vfile@6.0.1: | ||
| resolution: {integrity: sha512-1bYqc7pt6NIADBJ98UiG0Bn/CHIVOoZ/IyEkqIruLg0mE1BKzkOXY2D6CSqQIcKqgadppE5lrxgWXJmXd7zZJw==} | ||
|
|
||
| vite@5.2.11: |
There was a problem hiding this comment.
?import&raw) (update to 5.2.14)
The issue identified by the Trivy linter is a security vulnerability in the vite package version 5.2.11. The vulnerability, identified as CVE-2024-45811, allows for a bypass of the server.fs.deny configuration when using the ?import&raw query. This could potentially allow unauthorized access to file system paths that should be restricted, leading to security risks such as exposure of sensitive files.
To fix this issue, you need to update the vite package to a secure version that addresses this vulnerability. According to the issue description, updating to version 5.2.14 will resolve the problem. Here's the code suggestion to update the vite package version:
| vite@5.2.11: | |
| vite@5.2.14: |
This comment was generated by an experimental AI tool.
| domutils@3.1.0: | ||
| resolution: {integrity: sha512-H78uMmQtI2AhgDJjWeQmHwJJ2bLPD3GMmO7Zja/ZZh84wkm+4ut+IUnUdRa8uCGX88DiVx1j6FRe1XfxEgjEZA==} | ||
|
|
||
| dset@3.1.3: |
There was a problem hiding this comment.
❌ Codacy found a critical Security issue: Insecure dependency dset@3.1.3 (CVE-2024-21529: dset: Prototype Pollution) (update to 3.1.4)
The issue identified by the Trivy linter is a security vulnerability in the dset package, specifically version 3.1.3. The vulnerability is described as "Prototype Pollution" (CVE-2024-21529). Prototype Pollution is a type of security flaw that can allow an attacker to manipulate an object's prototype, potentially leading to unexpected behavior or security risks such as denial of service, arbitrary code execution, or data corruption.
To address this issue, the dset package should be updated to a version where the vulnerability is fixed, which in this case is version 3.1.4. Here is the code suggestion to update the package version:
| dset@3.1.3: | |
| dset@3.1.4: |
This comment was generated by an experimental AI tool.
Bumps micromatch from 4.0.7 to 4.0.8.
Release notes
Sourced from micromatch's releases.
Changelog
Sourced from micromatch's changelog.
Commits
8bd704e4.0.8a0e6841run verb to generate README documentation4ec2884Merge branch 'v4' into hauserkristof-feature/v4.0.803aa805Merge pull request #266 from hauserkristof/feature/v4.0.8814f5f7lint67fcce6fix: CHANGELOG about braces & CVE-2024-4068, v4.0.5113f2e3fix: CVE numbers in CHANGELOGd9dbd9afeat: updated CHANGELOG2ab1315fix: use actions/setup-node@v41406ea3feat: rework test to work on macos with node 10,12 and 14Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.
Summary by Sourcery
Bug Fixes: