Improper Authentication
Published 8 Mar 2021 · Updated 2 Dec 2024
Is your project on an affected Microsoft.Bot.Connector?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=4.6.0 <4.6.4
- Fixed in
- 4.6.4
dotnet add package Microsoft.Bot.Connector --version 4.6.4- Affected
- >=4.7.0 <4.7.3
- Fixed in
- 4.7.3
dotnet add package Microsoft.Bot.Connector --version 4.7.3- Affected
- >=4.8.0 <4.8.2
- Fixed in
- 4.8.2
dotnet add package Microsoft.Bot.Connector --version 4.8.2- Affected
- >=4.9.0 <4.9.5
- Fixed in
- 4.9.5
dotnet add package Microsoft.Bot.Connector --version 4.9.5- Affected
- >=4.10.0 <4.10.3
- Fixed in
- 4.10.3
dotnet add package Microsoft.Bot.Connector --version 4.10.3Details
Impact
A maliciously crafted claim may be incorrectly authenticated by the bot. Impacts bots that are not configured to be used as a Skill. This vulnerability requires an an attacker to have internal knowledge of the bot.
Patches
The problem has been patched in all affected versions. Please see the list of patched versions for the most appropriate one for your individual case.
Workarounds
Users who do not wish or are not able to upgrade can add an authentication configuration containing ClaimsValidator which throws an exception if the Claims are Skill Claims.
For detailed instructions, see the link in the References section.
For more information
If you have any questions or comments about this advisory:
- Open an issue in Microsoft Bot Builder SDK
- Email us at [bf-reports@microsoft.com](mailto:bf-reports@microsoft.com)
Is GHSA-qxx8-292g-2w66 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected Microsoft.Bot.Connector, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.