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 kind-of to 6.0.3 [security] #168

Merged
merged 1 commit into from
Nov 30, 2021

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 23, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change
kind-of 6.0.2 -> 6.0.3

GitHub Vulnerability Alerts

CVE-2019-20149

Versions of kind-of 6.x prior to 6.0.3 are vulnerable to a Validation Bypass. A maliciously crafted object can alter the result of the type check, allowing attackers to bypass the type checking validation.

Recommendation

Upgrade to versions 6.0.3 or later.


Configuration

📅 Schedule: "" (UTC).

🚦 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, click this checkbox.

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

@renovate renovate bot added the security label Nov 23, 2021
@renovate renovate bot force-pushed the renovate/npm-kind-of-vulnerability branch 5 times, most recently from 04bedbb to 2ca35cb Compare November 24, 2021 01:30
@renovate renovate bot force-pushed the renovate/npm-kind-of-vulnerability branch from 2ca35cb to 150cfed Compare November 24, 2021 10:20
@LinusU LinusU merged commit 6f3cfea into master Nov 30, 2021
@LinusU LinusU deleted the renovate/npm-kind-of-vulnerability branch November 30, 2021 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants