Exposure of Sensitive Information to an Unauthorized Actor in DisCatSharp
Published 22 Apr 2022 · Updated 8 Nov 2023
Is your project on an affected DisCatSharp?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=9.8.5 <9.9.1
- Fixed in
- 9.9.1
dotnet add package DisCatSharp --version 9.9.1Details
Impact
Users of versions 9.8.5, 9.8.6, 9.9.0 and previously published prereleases of 10.0.0 who have used either one of the two RequireDisCatSharpDeveloperAttributes or the BaseDiscordClient.LibraryDeveloperTeam have potentially had their bot token sent to a web server not affiliated with Discord. This server is owned and operated by DisCatSharp's development team. The tokens were not logged, yet it is still advisable to reset the tokens of potentially affected bots.
Patches
9.9.1 has been released to patch the issue for the current stable release and the current 10.0.0 prereleases are also no longer affected.
Workarounds
Remove all uses of the two RequireDisCatSharpDeveloperAttributes and all direct calls to BaseDiscordClient.LibraryDeveloperTeam.
Details
The HttpClient responsible for sending requests to the Discord API was erroneously reused to send requests to our website when DisCatSharp's team members were to be fetched.
For more information
If you have any questions or comments about this advisory:
- Join our Discord server
- Email us at [ottero@aitsys.dev](mailto:ottero@aitsys.dev)
Is GHSA-frxg-hf44-q765 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 DisCatSharp, and gives you the command that fixes it.
More advisories for DisCatSharp
- HighCVE-2017-0249High severity vulnerability that affects Microsoft.AspNetCore.Mvc · 16 Oct 2018
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.