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

chore(deps): update dependency nanoid to 3.1.31 [security] #419

Merged
merged 1 commit into from
Feb 23, 2022

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 9, 2022

WhiteSource Renovate

This PR contains the following updates:

Package Change
nanoid 3.1.25 -> 3.1.31
nanoid 3.1.20 -> 3.1.31

GitHub Vulnerability Alerts

CVE-2021-23566

The package nanoid before 3.1.31 are vulnerable to Information Exposure via the valueOf() function which allows to reproduce the last id generated.


Configuration

📅 Schedule: "" (UTC).

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


  • If you want to rebase/retry this PR, click this checkbox.

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

@renovate renovate bot force-pushed the renovate/npm-nanoid-vulnerability branch 12 times, most recently from f556214 to c1962ba Compare February 16, 2022 22:27
@renovate renovate bot force-pushed the renovate/npm-nanoid-vulnerability branch 2 times, most recently from e15be6f to 70334f2 Compare February 19, 2022 11:50
@renovate renovate bot force-pushed the renovate/npm-nanoid-vulnerability branch from 70334f2 to 2ebc583 Compare February 21, 2022 21:20
@sichen1234 sichen1234 merged commit b61635a into main Feb 23, 2022
@sichen1234 sichen1234 deleted the renovate/npm-nanoid-vulnerability branch February 23, 2022 02:09
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.

2 participants