-
Notifications
You must be signed in to change notification settings - Fork 4
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 tar to v6.2.1 [SECURITY] #606
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/npm-tar-vulnerability
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
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-tar-vulnerability
branch
2 times, most recently
from
April 25, 2024 10:26
9ad2c26
to
7719c94
Compare
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
April 25, 2024 23:34
7719c94
to
8245278
Compare
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
April 29, 2024 12:49
8245278
to
2c98e4e
Compare
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
April 29, 2024 13:51
2c98e4e
to
115d3d3
Compare
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
April 30, 2024 10:11
115d3d3
to
faf656d
Compare
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
April 30, 2024 17:09
faf656d
to
054dcc3
Compare
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
June 3, 2024 01:56
054dcc3
to
36267d9
Compare
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
2 times, most recently
from
June 17, 2024 22:13
c50fb60
to
c21cf17
Compare
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
July 6, 2024 02:35
c21cf17
to
f6d50e8
Compare
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
August 5, 2024 10:17
f6d50e8
to
0e6bf7b
Compare
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
August 22, 2024 00:21
0e6bf7b
to
30dba4c
Compare
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
August 23, 2024 20:02
30dba4c
to
f151a8a
Compare
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
August 28, 2024 16:17
f151a8a
to
cd7b2d2
Compare
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
September 4, 2024 09:36
cd7b2d2
to
6c40ffa
Compare
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
September 11, 2024 12:46
6c40ffa
to
dce398a
Compare
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
September 12, 2024 13:18
dce398a
to
e732936
Compare
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
September 16, 2024 10:13
e732936
to
8cfb6e5
Compare
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
September 24, 2024 13:04
8cfb6e5
to
1a49a11
Compare
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
October 4, 2024 22:58
1a49a11
to
d1178d3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
0 participants
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:
6.2.0
->6.2.1
GitHub Vulnerability Alerts
CVE-2024-28863
Description:
During some analysis today on npm's
node-tar
package I came across the folder creation process, Basicly if you provide node-tar with a path like this./a/b/c/foo.txt
it would create every folder and sub-folder here a, b and c until it reaches the last folder to createfoo.txt
, In-this case I noticed that there's no validation at all on the amount of folders being created, that said we're actually able to CPU and memory consume the system running node-tar and even crash the nodejs client within few seconds of running it using a path with too many sub-folders insideSteps To Reproduce:
You can reproduce this issue by downloading the tar file I provided in the resources and using node-tar to extract it, you should get the same behavior as the video
Proof Of Concept:
Here's a video show-casing the exploit:
Impact
Denial of service by crashing the nodejs client when attempting to parse a tar archive, make it run out of heap memory and consuming server CPU and memory resources
Report resources
payload.txt
archeive.tar.gz
Note
This report was originally reported to GitHub bug bounty program, they asked me to report it to you a month ago
Release Notes
isaacs/node-tar (tar)
v6.2.1
Compare Source
Configuration
📅 Schedule: Branch creation - "" in timezone Europe/London, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.