# GHSA-qxx8-292g-2w66: Improper Authentication

> A maliciously crafted claim can bypass authentication in Microsoft Bot Builder SDK bots not configured as Skills, requiring internal knowledge to exploit.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Mar 2021

## What is GHSA-qxx8-292g-2w66?

GHSA-qxx8-292g-2w66 is an authentication bypass vulnerability in Microsoft.Bot.Connector, published on 8 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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:
* Open an issue in [Microsoft Bot Builder SDK](https://github.com/microsoft/botbuilder-dotnet)
* Email us at [bf-reports@microsoft.com](mailto:bf-reports@microsoft.com)

## Which versions are affected by GHSA-qxx8-292g-2w66?

10 open source packages ship an affected version, including Microsoft.Bot.Connector.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Microsoft.Bot.Connector` | NuGet | From 4.10.0 | 4.10.3 |
| `Microsoft.Bot.Connector` | NuGet | From 4.10.0 | 4.10.3 |
| `Microsoft.Bot.Connector` | NuGet | From 4.6.0 | 4.6.4 |
| `Microsoft.Bot.Connector` | NuGet | From 4.6.0 | 4.6.4 |
| `Microsoft.Bot.Connector` | NuGet | From 4.7.0 | 4.7.3 |
| `Microsoft.Bot.Connector` | NuGet | From 4.7.0 | 4.7.3 |
| `Microsoft.Bot.Connector` | NuGet | From 4.8.0 | 4.8.2 |
| `Microsoft.Bot.Connector` | NuGet | From 4.8.0 | 4.8.2 |
| `Microsoft.Bot.Connector` | NuGet | From 4.9.0 | 4.9.5 |
| `Microsoft.Bot.Connector` | NuGet | From 4.9.0 | 4.9.5 |

## How do I fix GHSA-qxx8-292g-2w66?

Upgrade Microsoft.Bot.Connector to a fixed version for your release line: 4.10.3, 4.6.4, 4.7.3 or 4.8.2.

## Is GHSA-qxx8-292g-2w66 being exploited?

There is no known exploitation of GHSA-qxx8-292g-2w66 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-qxx8-292g-2w66 and fix it if it is affected.

What it is: GHSA-qxx8-292g-2w66 is an authentication bypass vulnerability in Microsoft.Bot.Connector, published on 8 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-qxx8-292g-2w66 in the wild and no public exploit code.

Affected packages and fixed versions:
- Microsoft.Bot.Connector (NuGet): affected from 4.10.0; fixed in 4.10.3
- Microsoft.Bot.Connector (NuGet): affected from 4.10.0; fixed in 4.10.3
- Microsoft.Bot.Connector (NuGet): affected from 4.6.0; fixed in 4.6.4
- Microsoft.Bot.Connector (NuGet): affected from 4.6.0; fixed in 4.6.4
- Microsoft.Bot.Connector (NuGet): affected from 4.7.0; fixed in 4.7.3
- Microsoft.Bot.Connector (NuGet): affected from 4.7.0; fixed in 4.7.3
- Microsoft.Bot.Connector (NuGet): affected from 4.8.0; fixed in 4.8.2
- Microsoft.Bot.Connector (NuGet): affected from 4.8.0; fixed in 4.8.2
- Microsoft.Bot.Connector (NuGet): affected from 4.9.0; fixed in 4.9.5
- Microsoft.Bot.Connector (NuGet): affected from 4.9.0; fixed in 4.9.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-qxx8-292g-2w66/ (Markdown: https://insights.sbomify.com/GHSA-qxx8-292g-2w66/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-qxx8-292g-2w66

---
From sbomify Insights: https://insights.sbomify.com/GHSA-qxx8-292g-2w66/
Summaries are generated and may contain mistakes; the official description above is the record.