Skip to content
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] #1134

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Apr 14, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
tar 6.2.0 -> 6.2.1 age adoption passing confidence
tar ^6.1.13 -> ^6.2.1 age adoption passing confidence

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 create foo.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 inside

Steps 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 these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner April 14, 2024 00:05
@renovate renovate bot added the dependencies Pull requests that update a dependency file label Apr 14, 2024
@renovate renovate bot force-pushed the renovate/npm-tar-vulnerability branch 2 times, most recently from ca309e5 to 0e5b9c7 Compare April 26, 2024 17:56
@renovate renovate bot force-pushed the renovate/npm-tar-vulnerability branch from 0e5b9c7 to 5f6b701 Compare June 4, 2024 17:36
@renovate renovate bot force-pushed the renovate/npm-tar-vulnerability branch from 5f6b701 to 6467a53 Compare July 22, 2024 06:02
@renovate renovate bot force-pushed the renovate/npm-tar-vulnerability branch from 6467a53 to 597f947 Compare August 11, 2024 12:00
@renovate renovate bot force-pushed the renovate/npm-tar-vulnerability branch from 597f947 to c3b8cc9 Compare August 28, 2024 20:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants