Skip to content

Exposure of Sensitive Information to an Unauthorized Actor in DisCatSharp

Moderate severity GitHub Reviewed Published Apr 13, 2022 in Aiko-IT-Systems/DisCatSharp • Updated Jan 27, 2023

Package

nuget DisCatSharp (NuGet)

Affected versions

>= 9.8.5, < 9.9.1

Patched versions

9.9.1

Description

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:

References

@Saalvage Saalvage published to Aiko-IT-Systems/DisCatSharp Apr 13, 2022
Published by the National Vulnerability Database Apr 14, 2022
Published to the GitHub Advisory Database Apr 22, 2022
Reviewed Apr 22, 2022
Last updated Jan 27, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

EPSS score

0.150%
(52nd percentile)

Weaknesses

CVE ID

CVE-2022-24849

GHSA ID

GHSA-frxg-hf44-q765
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.