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] - autoclosed #67

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 11, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
tar 6.2.0 -> 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 - "" (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.


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

This PR has been generated by Mend Renovate. View repository job log here.

Copy link
Contributor

github-actions bot commented Apr 11, 2024

πŸ¦™ MegaLinter status: ❌ ERROR

Descriptor Linter Files Fixed Errors Elapsed time
βœ… ACTION actionlint 3 0 0.04s
βœ… COPYPASTE jscpd yes no 1.58s
βœ… JAVASCRIPT eslint 3 0 0 1.01s
βœ… JAVASCRIPT prettier 3 0 0 0.93s
βœ… JSON eslint-plugin-jsonc 10 0 0 1.4s
βœ… JSON jsonlint 10 0 0.25s
βœ… JSON npm-package-json-lint yes no 0.57s
βœ… JSON prettier 10 0 0 0.56s
βœ… JSON v8r 10 0 20.45s
βœ… MARKDOWN markdownlint 2 0 0 0.66s
⚠️ MARKDOWN markdown-link-check 3 2 4.48s
βœ… MARKDOWN markdown-table-formatter 3 0 0 0.39s
βœ… REPOSITORY checkov yes no 12.08s
βœ… REPOSITORY gitleaks yes no 0.43s
βœ… REPOSITORY git_diff yes no 0.03s
❌ REPOSITORY grype yes 1 12.22s
βœ… REPOSITORY secretlint yes no 0.76s
βœ… REPOSITORY trivy yes no 5.46s
βœ… REPOSITORY trivy-sbom yes no 1.92s
βœ… REPOSITORY trufflehog yes no 7.39s
βœ… SPELL cspell 31 0 3.07s
βœ… SPELL lychee 20 0 1.14s
βœ… XML xmllint 5 0 0 0.01s
βœ… YAML prettier 7 0 0 0.84s
βœ… YAML v8r 6 0 11.05s
βœ… YAML yamllint 7 0 0.34s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by OX Security

@renovate renovate bot changed the title Update dependency tar to v6.2.1 [SECURITY] Update dependency tar to v6.2.1 [SECURITY] - autoclosed May 8, 2024
@renovate renovate bot closed this May 8, 2024
@renovate renovate bot deleted the renovate/npm-tar-vulnerability branch May 8, 2024 11:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants