Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET NuGet
Not in CISA KEV

Improper AuthenticationGHSA-qxx8-292g-2w66

GHSA-qxx8-292g-2w66 is a security vulnerability in Microsoft.Bot.Connector. A fix is available for Microsoft.Bot.Connector — see the affected versions and patch details below.

Published
Updated
Affected
5 pkgs
Patched
5 / 5
Exploits
None indexed
Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

5 pkgs affected
.NETMicrosoft.Bot.Connector.NETMicrosoft.Bot.Connector.NETMicrosoft.Bot.Connector.NETMicrosoft.Bot.Connector.NETMicrosoft.Bot.Connector

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

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:

Affected Packages

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetMicrosoft.Bot.Connector≥ 4.6.0&&< 4.6.44.6.4dotnet add package Microsoft.Bot.Connector --version 4.6.4
.NETNuGetMicrosoft.Bot.Connector≥ 4.7.0&&< 4.7.34.7.3dotnet add package Microsoft.Bot.Connector --version 4.7.3
.NETNuGetMicrosoft.Bot.Connector≥ 4.8.0&&< 4.8.24.8.2dotnet add package Microsoft.Bot.Connector --version 4.8.2
.NETNuGetMicrosoft.Bot.Connector≥ 4.9.0&&< 4.9.54.9.5dotnet add package Microsoft.Bot.Connector --version 4.9.5
.NETNuGetMicrosoft.Bot.Connector≥ 4.10.0&&< 4.10.34.10.3dotnet add package Microsoft.Bot.Connector --version 4.10.3

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.Bot.Connector, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update Microsoft.Bot.Connector to 4.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qxx8-292g-2w66 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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 instru
O3 Security · Impact-Aware SCA

Is GHSA-qxx8-292g-2w66 in your dependencies?

Find it across NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works
Improper Authentication