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

fix(deps): update dependency nanoid to v5.0.9 [security] #2016

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 10, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
nanoid 5.0.7 -> 5.0.9 age adoption passing confidence

Review

  • Updates have been tested and work
  • If updates are AWS related, versions match the infrastructure (e.g. Lambda runtime, database, etc.)

GitHub Vulnerability Alerts

CVE-2024-55565

When nanoid is called with a fractional value, there were a number of undesirable effects:

  1. in browser and non-secure, the code infinite loops on while (size--)
  2. in node, the value of poolOffset becomes fractional, causing calls to nanoid to return zeroes until the pool is next filled
  3. if the first call in node is a fractional argument, the initial buffer allocation fails with an error

Version 3.3.8 and 5.0.9 are fixed.


Release Notes

ai/nanoid (nanoid)

v5.0.9

Compare Source

  • Fixed a way to break Nano ID by passing non-integer size (by @​myndzi).

v5.0.8

Compare Source


Configuration

📅 Schedule: Branch creation - "" in timezone America/Montreal, 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.


  • 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 force-pushed the renovate/npm-nanoid-vulnerability branch 3 times, most recently from aded82c to 1a70777 Compare December 13, 2024 18:20
@renovate renovate bot force-pushed the renovate/npm-nanoid-vulnerability branch from 1a70777 to 1eea25e Compare December 18, 2024 18:29
@renovate renovate bot force-pushed the renovate/npm-nanoid-vulnerability branch 15 times, most recently from 0bb998f to d94b491 Compare January 9, 2025 19:03
@renovate renovate bot force-pushed the renovate/npm-nanoid-vulnerability branch 6 times, most recently from 047cb65 to 0b5cd89 Compare January 15, 2025 14:51
@renovate renovate bot force-pushed the renovate/npm-nanoid-vulnerability branch 3 times, most recently from 193fa4f to 4af2483 Compare January 20, 2025 20:09
@renovate renovate bot force-pushed the renovate/npm-nanoid-vulnerability branch 10 times, most recently from d068fc1 to 9185f2e Compare February 13, 2025 12:33
@renovate renovate bot force-pushed the renovate/npm-nanoid-vulnerability branch 9 times, most recently from 14cc8a1 to 8c866e5 Compare February 20, 2025 15:38
@renovate renovate bot force-pushed the renovate/npm-nanoid-vulnerability branch 9 times, most recently from 7b4e051 to ea0ae5e Compare February 27, 2025 20:17
@renovate renovate bot force-pushed the renovate/npm-nanoid-vulnerability branch from ea0ae5e to 23d9972 Compare March 3, 2025 18:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants