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.

Sign up for GitHub

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

Jump to bottom

🚨 [security] Update lerna 8.1.2 → 8.1.3 (patch) #83

Closed
wants to merge 1 commit into from
Closed

🚨 [security] Update lerna 8.1.2 → 8.1.3 (patch) #83

wants to merge 1 commit into from

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented May 14, 2024

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ lerna (8.1.2 → 8.1.3) · Repo · Changelog

Release Notes

8.1.3

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​npmcli/git (indirect, 5.0.4 → 5.0.7) · Repo · Changelog

Release Notes

5.0.7

More info than we can show here.

5.0.6

More info than we can show here.

5.0.5

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​nrwl/devkit (indirect, 18.0.4 → 19.0.3) · Repo

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​nrwl/tao (indirect, 18.0.4 → 19.0.3) · Repo

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​nx/devkit (indirect, 18.0.4 → 19.0.3) · Repo

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ agent-base (indirect, 7.1.0 → 7.1.1) · Repo

Sorry, we couldn't find anything useful about this release.

↗️ axios (indirect, 1.6.7 → 1.6.8) · Repo · Changelog

Release Notes

1.6.8

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ cacache (indirect, 18.0.2 → 18.0.3) · Repo · Changelog

Release Notes

18.0.3

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ ejs (indirect, 3.1.9 → 3.1.10) · Repo · Changelog

Security Advisories 🚨

🚨 ejs lacks certain pollution protection

The ejs (aka Embedded JavaScript templates) package before 3.1.10 for Node.js lacks certain pollution protection.

Release Notes

3.1.10

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ follow-redirects (indirect, 1.15.5 → 1.15.6) · Repo

Security Advisories 🚨

🚨 follow-redirects' Proxy-Authorization header kept across hosts

When using axios, its dependency follow-redirects only clears authorization header during cross-domain redirect, but allows the proxy-authentication header which contains credentials too.

Steps To Reproduce & PoC

Test code:

const axios = require('axios');

axios.get('http://127.0.0.1:10081/', {

headers: {

'AuThorization': 'Rear Test',

'ProXy-AuthoriZation': 'Rear Test',

'coOkie': 't=1'

}

})

.then((response) => {

console.log(response);

})

When I meet the cross-domain redirect, the sensitive headers like authorization and cookie are cleared, but proxy-authentication header is kept.

Impact

This vulnerability may lead to credentials leak.

Recommendations

Remove proxy-authentication header during cross-domain redirect

Recommended Patch

follow-redirects/index.js:464

- removeMatchingHeaders(/^(?:authorization|cookie)$/i, this._options.headers);
+ removeMatchingHeaders(/^(?:authorization|proxy-authorization|cookie)$/i, this._options.headers);
Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ hosted-git-info (indirect, 7.0.1 → 7.0.2) · Repo · Changelog

Release Notes

7.0.2

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ ignore-walk (indirect, 6.0.4 → 6.0.5) · Repo · Changelog

Release Notes

6.0.5

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ jake (indirect, 10.8.7 → 10.9.1) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ json-parse-even-better-errors (indirect, 3.0.1 → 3.0.2) · Repo · Changelog

Release Notes

3.0.2

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ make-fetch-happen (indirect, 13.0.0 → 13.0.1) · Repo · Changelog

Release Notes

13.0.1

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ node-gyp (indirect, 10.0.1 → 10.1.0) · Repo · Changelog

Release Notes

10.1.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ nopt (indirect, 7.2.0 → 7.2.1) · Repo · Changelog

Release Notes

7.2.1

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ normalize-package-data (indirect, 6.0.0 → 6.0.1) · Repo · Changelog

Release Notes

6.0.1

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ npm-package-arg (indirect, 11.0.1 → 11.0.2) · Repo · Changelog

Release Notes

11.0.2

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ npm-pick-manifest (indirect, 9.0.0 → 9.0.1) · Repo · Changelog

Release Notes

9.0.1

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ npm-registry-fetch (indirect, 16.1.0 → 16.2.1) · Repo · Changelog

Release Notes

16.2.1

More info than we can show here.

16.2.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ nx (indirect, 18.0.4 → 19.0.3) · Repo

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ pacote (indirect, 17.0.6 → 17.0.7) · Repo · Changelog

Release Notes

17.0.7

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ react-is (indirect, 18.2.0 → 18.3.1) · Repo · Changelog

Release Notes

18.3.1

More info than we can show here.

18.3.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ read-package-json (indirect, 7.0.0 → 7.0.1) · Repo · Changelog

Release Notes

7.0.1

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ socks-proxy-agent (indirect, 8.0.2 → 8.0.3) · Repo · Changelog

↗️ tar (indirect, 6.1.11 → 6.2.1) · Repo · Changelog

Security Advisories 🚨

🚨 Denial of service while parsing a tar file due to lack of folders count validation

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

6.1.13

More info than we can show here.

6.1.12

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ tmp (indirect, 0.2.1 → 0.2.3) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ typescript (indirect, 5.3.3 → 5.4.5) · Repo

Release Notes

5.4.5

More info than we can show here.

5.4.4

More info than we can show here.

5.4.3

More info than we can show here.

5.4.2

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

🆕 @​npmcli/redact (added, 1.1.0)

🆕 lru-cache (added, 10.2.2)

🆕 minimatch (added, 9.0.4)

🆕 semver (added, 7.6.2)

🆕 ssri (added, 10.0.6)

🆕 proc-log (added, 4.2.0)

🆕 read (added, 3.0.1)

🗑️ @​restorecommerce/dataset-demoshop-catalog-transformer (removed)

🗑️ @​restorecommerce/dataset-system-units-transformer (removed)

🗑️ csv-parser (removed)

🗑️ node-xlsx (removed)

🗑️ object-hash (removed)

🗑️ xlsx (removed)

🗑️ uuid (removed)

🗑️ through2 (removed)

Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added the depfu label May 14, 2024
@bugerry87 bugerry87 closed this May 15, 2024
@bugerry87 bugerry87 deleted the depfu/update/npm/lerna-8.1.3 branch May 15, 2024 11:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
depfu
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@bugerry87