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

[Snyk] Upgrade botbuilder from 4.22.2 to 4.23.1 #500

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

Conversation

DevangPatelUK
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade botbuilder from 4.22.2 to 4.23.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 13 versions ahead of your current version.

  • The recommended version was released on a month ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Denial of Service (DoS)
SNYK-JS-WS-7266574
696 Proof of Concept
high severity Prototype Pollution
SNYK-JS-AXIOS-6144788
696 No Known Exploit
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-AXIOS-6124857
696 Proof of Concept
medium severity Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
SNYK-JS-AZUREIDENTITY-7246760
696 No Known Exploit
medium severity Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
SNYK-JS-AZUREMSALNODE-7246761
696 No Known Exploit
Release notes
Package name: botbuilder

Snyk has created this PR to upgrade botbuilder from 4.22.2 to 4.23.1.

See this package in npm:
botbuilder

See this project in Snyk:
https://app.snyk.io/org/ibmstudent/project/7f15bbf8-1ba1-455b-aafa-2f20a4963111?utm_source=github&utm_medium=referral&page=upgrade-pr
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