Bumps tar from 4.4.1 to 4.4.13. This update includes security fixes.
Vulnerabilities fixed
*Sourced from The GitHub Security Advisory Database.*
> **High severity vulnerability that affects tar**
> A vulnerability was found in node-tar before version 4.4.2. An Arbitrary File Overwrite issue exists when extracting a tarball containing a hardlink to a file that already exists on the system, in conjunction with a later plain file with the same name as the hardlink. This plain file content replaces the existing file content.
>
> Affected versions: >= 3.0.0 < 4.4.2
*Sourced from The GitHub Security Advisory Database.*
> **High severity vulnerability that affects tar**
> A vulnerability was found in node-tar before version 4.4.2. An Arbitrary File Overwrite issue exists when extracting a tarball containing a hardlink to a file that already exists on the system, in conjunction with a later plain file with the same name as the hardlink. This plain file content replaces the existing file content.
>
> Affected versions: < 4.4.2
Commits
- [`65edb39`](https://github.com/npm/node-tar/commit/65edb39114ad5956c06f8d7893365e942042ede1) 4.4.13
- [`d04c3ff`](https://github.com/npm/node-tar/commit/d04c3ffb41a0d2bbae926a38d3456ebda0249565) Always provide a callback to fs.close()
- [`dbd6f52`](https://github.com/npm/node-tar/commit/dbd6f52ba9cdfbce2a28d8cd28a016bc3435946a) 4.4.12
- [`0240086`](https://github.com/npm/node-tar/commit/0240086746b72c3080598ea2a2ba6ad85de9ec08) update tap and minipass
- [`9232b3d`](https://github.com/npm/node-tar/commit/9232b3d7da934c142e3d0ab97ef35ec0ba3917fc) 4.4.11
- [`42fe53b`](https://github.com/npm/node-tar/commit/42fe53b413527983f2509ae606412ee1e93761d7) update minipass, pre-pause ReadEntry objects
- [`4a9069a`](https://github.com/npm/node-tar/commit/4a9069a0a2308e9eed063f648820c4d5859b02d3) wrapped new header with try catch
- [`84ab44d`](https://github.com/npm/node-tar/commit/84ab44d8201e04139f3635685ce7ea2c2e20710a) 4.4.10
- [`77522f0`](https://github.com/npm/node-tar/commit/77522f066e6782775114cf78e9491d67b259ab0d) Use `stat` instead of `lstat` when checking CWD
- [`49058cb`](https://github.com/npm/node-tar/commit/49058cb8f2a2e2574152353b391fbec0a7b3fe97) use --follow-tags on git publish push
- Additional commits viewable in [compare view](https://github.com/npm/node-tar/compare/v4.4.1...v4.4.13)
Dependabot 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 rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in the `.dependabot/config.yml` file in this repo:
- Update frequency
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
Finally, you can contact us by mentioning @dependabot.
Bumps tar from 4.4.1 to 4.4.13. This update includes security fixes.
Vulnerabilities fixed
*Sourced from The GitHub Security Advisory Database.* > **High severity vulnerability that affects tar** > A vulnerability was found in node-tar before version 4.4.2. An Arbitrary File Overwrite issue exists when extracting a tarball containing a hardlink to a file that already exists on the system, in conjunction with a later plain file with the same name as the hardlink. This plain file content replaces the existing file content. > > Affected versions: >= 3.0.0 < 4.4.2 *Sourced from The GitHub Security Advisory Database.* > **High severity vulnerability that affects tar** > A vulnerability was found in node-tar before version 4.4.2. An Arbitrary File Overwrite issue exists when extracting a tarball containing a hardlink to a file that already exists on the system, in conjunction with a later plain file with the same name as the hardlink. This plain file content replaces the existing file content. > > Affected versions: < 4.4.2Commits
- [`65edb39`](https://github.com/npm/node-tar/commit/65edb39114ad5956c06f8d7893365e942042ede1) 4.4.13 - [`d04c3ff`](https://github.com/npm/node-tar/commit/d04c3ffb41a0d2bbae926a38d3456ebda0249565) Always provide a callback to fs.close() - [`dbd6f52`](https://github.com/npm/node-tar/commit/dbd6f52ba9cdfbce2a28d8cd28a016bc3435946a) 4.4.12 - [`0240086`](https://github.com/npm/node-tar/commit/0240086746b72c3080598ea2a2ba6ad85de9ec08) update tap and minipass - [`9232b3d`](https://github.com/npm/node-tar/commit/9232b3d7da934c142e3d0ab97ef35ec0ba3917fc) 4.4.11 - [`42fe53b`](https://github.com/npm/node-tar/commit/42fe53b413527983f2509ae606412ee1e93761d7) update minipass, pre-pause ReadEntry objects - [`4a9069a`](https://github.com/npm/node-tar/commit/4a9069a0a2308e9eed063f648820c4d5859b02d3) wrapped new header with try catch - [`84ab44d`](https://github.com/npm/node-tar/commit/84ab44d8201e04139f3635685ce7ea2c2e20710a) 4.4.10 - [`77522f0`](https://github.com/npm/node-tar/commit/77522f066e6782775114cf78e9491d67b259ab0d) Use `stat` instead of `lstat` when checking CWD - [`49058cb`](https://github.com/npm/node-tar/commit/49058cb8f2a2e2574152353b391fbec0a7b3fe97) use --follow-tags on git publish push - Additional commits viewable in [compare view](https://github.com/npm/node-tar/compare/v4.4.1...v4.4.13)Dependabot 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 rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in the `.dependabot/config.yml` file in this repo: - Update frequency - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot.