-
Notifications
You must be signed in to change notification settings - Fork 0
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 [SECURITY] - autoclosed #36
Closed
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
Benchmark Test ResultsBenchmark results from the latest changes vs base branch
|
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
April 14, 2024 17:49
e7d65ae
to
ad2eff1
Compare
renovate
bot
changed the title
Update dependency tar to v6 [SECURITY]
Update dependency tar to v7 [SECURITY]
Apr 14, 2024
renovate
bot
changed the title
Update dependency tar to v7 [SECURITY]
Update dependency tar to v6 [SECURITY]
Apr 14, 2024
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
2 times, most recently
from
April 21, 2024 17:34
463a6ec
to
54e5290
Compare
renovate
bot
changed the title
Update dependency tar to v6 [SECURITY]
Update dependency tar to v7 [SECURITY]
Apr 21, 2024
renovate
bot
changed the title
Update dependency tar to v7 [SECURITY]
Update dependency tar to v6 [SECURITY]
Apr 21, 2024
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
2 times, most recently
from
April 26, 2024 23:53
e4a6175
to
3dcba36
Compare
renovate
bot
changed the title
Update dependency tar to v6 [SECURITY]
Update dependency tar to v7 [SECURITY]
Apr 26, 2024
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
April 26, 2024 23:54
3dcba36
to
6689095
Compare
renovate
bot
changed the title
Update dependency tar to v7 [SECURITY]
Update dependency tar to v6 [SECURITY]
Apr 26, 2024
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
May 2, 2024 17:17
6689095
to
9b58475
Compare
renovate
bot
changed the title
Update dependency tar to v6 [SECURITY]
Update dependency tar to v7 [SECURITY]
May 2, 2024
renovate
bot
changed the title
Update dependency tar to v7 [SECURITY]
Update dependency tar to v6 [SECURITY]
May 2, 2024
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
May 2, 2024 17:18
9b58475
to
cd294dd
Compare
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
May 10, 2024 05:37
cd294dd
to
6679a77
Compare
renovate
bot
changed the title
Update dependency tar to v6 [SECURITY]
Update dependency tar to v7 [SECURITY]
May 10, 2024
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
May 10, 2024 05:37
6679a77
to
e097163
Compare
renovate
bot
changed the title
Update dependency tar to v7 [SECURITY]
Update dependency tar to v6 [SECURITY]
May 10, 2024
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
May 23, 2024 05:49
e097163
to
fe36d09
Compare
renovate
bot
changed the title
Update dependency tar to v6 [SECURITY]
Update dependency tar to v7 [SECURITY]
May 23, 2024
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
May 23, 2024 05:50
fe36d09
to
a26ea85
Compare
renovate
bot
changed the title
Update dependency tar to v7 [SECURITY]
Update dependency tar to v6 [SECURITY]
May 23, 2024
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
June 5, 2024 17:56
a26ea85
to
de22410
Compare
renovate
bot
changed the title
Update dependency tar to v6 [SECURITY]
Update dependency tar to v7 [SECURITY]
Jun 5, 2024
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
June 5, 2024 17:57
de22410
to
ccaa3b3
Compare
renovate
bot
changed the title
Update dependency tar to v7 [SECURITY]
Update dependency tar to v6 [SECURITY]
Jun 5, 2024
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
June 19, 2024 17:42
ccaa3b3
to
9a14bd2
Compare
renovate
bot
changed the title
Update dependency tar to v6 [SECURITY]
Update dependency tar to v7 [SECURITY]
Jun 19, 2024
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
June 19, 2024 17:43
9a14bd2
to
7a09262
Compare
renovate
bot
changed the title
Update dependency tar to v7 [SECURITY]
Update dependency tar to v6 [SECURITY]
Jun 19, 2024
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
June 28, 2024 08:38
7a09262
to
2c425ca
Compare
renovate
bot
changed the title
Update dependency tar to v6 [SECURITY]
Update dependency tar to v7 [SECURITY]
Jun 28, 2024
renovate
bot
changed the title
Update dependency tar to v7 [SECURITY]
Update dependency tar to v6 [SECURITY]
Jun 28, 2024
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
June 28, 2024 08:38
2c425ca
to
c560dee
Compare
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
July 15, 2024 17:52
c560dee
to
63bb7d8
Compare
renovate
bot
changed the title
Update dependency tar to v6 [SECURITY]
Update dependency tar to v7 [SECURITY]
Jul 15, 2024
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
July 15, 2024 17:54
63bb7d8
to
226e034
Compare
renovate
bot
changed the title
Update dependency tar to v7 [SECURITY]
Update dependency tar to v6 [SECURITY]
Jul 15, 2024
renovate
bot
changed the title
Update dependency tar to v6 [SECURITY]
Update dependency tar to v7 [SECURITY]
Jul 23, 2024
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
2 times, most recently
from
July 23, 2024 23:44
0da5d29
to
5f7e441
Compare
renovate
bot
changed the title
Update dependency tar to v7 [SECURITY]
Update dependency tar to v6 [SECURITY]
Jul 23, 2024
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
July 28, 2024 14:54
5f7e441
to
504a716
Compare
renovate
bot
changed the title
Update dependency tar to v6 [SECURITY]
Update dependency tar to v7 [SECURITY]
Jul 28, 2024
renovate
bot
changed the title
Update dependency tar to v7 [SECURITY]
Update dependency tar to v6 [SECURITY]
Jul 28, 2024
renovate
bot
force-pushed
the
renovate/npm-tar-vulnerability
branch
from
July 28, 2024 14:55
504a716
to
ea99b88
Compare
renovate
bot
changed the title
Update dependency tar to v6 [SECURITY]
Update dependency tar to v6 [SECURITY] - autoclosed
Aug 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
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:
^4.4.13
->^6.2.1
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
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
v6.2.0
Compare Source
v6.1.15
Compare Source
v6.1.14
Compare Source
v6.1.13
Compare Source
Dependencies
cc4e0dd
#343 bump minipass from 3.3.6 to 4.0.0v6.1.12
Compare Source
Bug Fixes
57493ee
#332 ensuring close event is emited after stream has ended (@webark)b003c64
#314 replace deprecated String.prototype.substr() (#314) (@CommanderRoot, @lukekarrys)Documentation
f129929
#313 remove dead link to benchmarks (#313) (@yetzt)c1faa9f
add examples/explanation of using tar.t (@isaacs)v6.1.11
Compare Source
v6.1.10
Compare Source
v6.1.9
Compare Source
v6.1.8
Compare Source
v6.1.7
Compare Source
v6.1.6
Compare Source
v6.1.5
Compare Source
v6.1.4
Compare Source
v6.1.3
Compare Source
v6.1.2
Compare Source
v6.1.1
Compare Source
Dependencies
cc4e0dd
#343 bump minipass from 3.3.6 to 4.0.0v6.1.0
Compare Source
v6.0.5
Compare Source
v6.0.4
Compare Source
v6.0.3
Compare Source
v6.0.2
Compare Source
v6.0.1
Compare Source
v6.0.0
Compare Source
v5.0.11
Compare Source
v5.0.10
Compare Source
v5.0.9
Compare Source
v5.0.8
Compare Source
v5.0.7
Compare Source
v5.0.6
Compare Source
v5.0.5
Compare Source
v5.0.4
Compare Source
v5.0.2
Compare Source
v5.0.1
Compare Source
v5.0.0
Compare Source
v4.4.19
Compare Source
v4.4.18
Compare Source
v4.4.17
Compare Source
v4.4.16
Compare Source
v4.4.15
Compare Source
v4.4.14
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.
🔕 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.