BotSharp through 5.2.0 Authentication Bypass via Hard-Coded JWT Signing Key
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| SciSharp | BotSharp | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Scisharp | Botsharp |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.476% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Scisharp
Scisharp botsharp |
|
| Vendors & Products |
Scisharp
Scisharp botsharp |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | BotSharp through 5.2.0 contains an authentication bypass vulnerability that allows unauthenticated remote attackers to forge bearer tokens using the hard-coded Jwt:Key in WebStarter appsettings.json. Attackers can sign tokens with the committed HMAC secret and fixed botsharp issuer and audience to impersonate any known user, including administrators, on Authorize-protected API routes. | |
| Title | BotSharp through 5.2.0 Authentication Bypass via Hard-Coded JWT Signing Key | |
| Weaknesses | CWE-321 | |
| References |
|
|
| Metrics |
cvssV3_1
|