Skip to content

[Snyk] Upgrade botbuilder from 4.22.2 to 4.22.3#302

Open
DevangPatelUK wants to merge 1 commit intomainfrom
snyk-upgrade-bbbd3547b88a8c39e673353d1f8ef8a2
Open

[Snyk] Upgrade botbuilder from 4.22.2 to 4.22.3#302
DevangPatelUK wants to merge 1 commit intomainfrom
snyk-upgrade-bbbd3547b88a8c39e673353d1f8ef8a2

Conversation

@DevangPatelUK
Copy link
Copy Markdown
Owner

snyk-top-banner

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

ℹ️ 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 1 version ahead of your current version.

  • The recommended version was released on 3 months 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
Release notes
Package name: botbuilder from botbuilder GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

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

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