[PR #50] [MERGED] [Security] Bump tar from 2.2.1 to 2.2.2 #58

New issue

Closed

opened 2026-02-26 04:36:42 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 04:36:42 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/moollaza/repo-remover/pull/50
Author: @dependabot-preview[bot]
Created: 12/16/2019
Status: ✅ Merged
Merged: 12/19/2019
Merged by: @moollaza

Base: master ← Head: dependabot/npm_and_yarn/tar-2.2.2

📝 Commits (1)

9dd949d [Security] Bump tar from 2.2.1 to 2.2.2

📊 Changes

1 file changed (+17 additions, -34 deletions)

View changed files

📝 yarn.lock (+17 -34)

📄 Description

Bumps tar from 2.2.1 to 2.2.2. This update includes a security fix.

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: < 2.2.2

Commits

523c5c7 2.2.2
7ecef07 Bump fstream to fix hardlink overwriting vulnerability
9fc84b9 Use {} for hardlink tracking instead of []
15e59f1 Only track previously seen hardlinks
4f85851 Ignore potentially unsafe files
See full diff in compare view

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 use these labels will set the current labels as the default for future PRs for this repo and language
@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
@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 your Dependabot dashboard:

Update frequency (including time of day and day of week)
Pull request limits (per update run and/or open at any time)
Out-of-range updates (receive only lockfile updates, if desired)
Security updates (receive only security updates, if desired)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/moollaza/repo-remover/pull/50 **Author:** [@dependabot-preview[bot]](https://github.com/apps/dependabot-preview) **Created:** 12/16/2019 **Status:** ✅ Merged **Merged:** 12/19/2019 **Merged by:** [@moollaza](https://github.com/moollaza) **Base:** `master` ← **Head:** `dependabot/npm_and_yarn/tar-2.2.2` --- ### 📝 Commits (1) - [`9dd949d`](https://github.com/moollaza/repo-remover/commit/9dd949d7b60704d9158c8d407911c258a7a8ab85) [Security] Bump tar from 2.2.1 to 2.2.2 ### 📊 Changes **1 file changed** (+17 additions, -34 deletions) <details> <summary>View changed files</summary> 📝 `yarn.lock` (+17 -34) </details> ### 📄 Description Bumps [tar](https://github.com/npm/node-tar) from 2.2.1 to 2.2.2. **This update includes a security fix.** <details> <summary>Vulnerabilities fixed</summary> *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: < 2.2.2 </details> <details> <summary>Commits</summary> - [`523c5c7`](https://github.com/npm/node-tar/commit/523c5c7fef48b10811fccd12b42803c61b6aead8) 2.2.2 - [`7ecef07`](https://github.com/npm/node-tar/commit/7ecef07da6a9e72cc0c4d0c9c6a8e85b6b52395d) Bump fstream to fix hardlink overwriting vulnerability - [`9fc84b9`](https://github.com/npm/node-tar/commit/9fc84b9c596c3589d4c1ab050843de0eafb002e8) Use {} for hardlink tracking instead of [] - [`15e59f1`](https://github.com/npm/node-tar/commit/15e59f1d671ffbe4ae7c74dafcbec93ea2584e34) Only track previously seen hardlinks - [`4f85851`](https://github.com/npm/node-tar/commit/4f8585178af78f8f64c5ca38e923c306613278b9) Ignore potentially unsafe files - See full diff in [compare view](https://github.com/npm/node-tar/compare/v2.2.1...v2.2.2) </details> <br /> [![Dependabot compatibility score](https://api.dependabot.com/badges/compatibility_score?dependency-name=tar&package-manager=npm_and_yarn&previous-version=2.2.1&new-version=2.2.2)](https://dependabot.com/compatibility-score.html?dependency-name=tar&package-manager=npm_and_yarn&previous-version=2.2.1&new-version=2.2.2) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@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 your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>