GHSA-5jq8-q6rj-9gq4
First published: Thu Jul 11 2024(Updated: )
### Impact Due to a bug in Red's Core API, 3rd-party cogs using the [`@commands.can_manage_channel()`](https://docs.discord.red/en/stable/framework_checks.html#redbot.core.commands.can_manage_channel) command permission check without additional permission controls may authorize a user to run a command even when that user doesn't have permissions to manage a channel. None of the core commands or core cogs are affected. The maintainers of the project are not aware of any _public_ 3rd-party cog utilizing this API at the time of writing this advisory. The [`@commands.mod_or_can_manage_channel()`](https://docs.discord.red/en/stable/framework_checks.html#redbot.core.commands.mod_or_can_manage_channel), [`@commands.admin_or_can_manage_channel()`](https://docs.discord.red/en/stable/framework_checks.html#redbot.core.commands.admin_or_can_manage_channel), and [`@commands.guildowner_or_can_manage_channel()`](https://docs.discord.red/en/stable/framework_checks.html#redbot.core.commands.guildowner_or_can_manage_channel) command permission checks are unaffected. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N/AU:Y/R:U/RE:L ### Patches The problem was patched in PR #6398 and later released in version [3.5.10](https://pypi.org/project/Red-DiscordBot/3.5.10/). ### Workarounds Any cog using the [`@commands.can_manage_channel()`](https://docs.discord.red/en/stable/framework_checks.html#redbot.core.commands.can_manage_channel) command permission check should be unloaded until an upgrade to a patched version can be performed. ### References https://github.com/Cog-Creators/Red-DiscordBot/pull/6398 https://github.com/Cog-Creators/Red-DiscordBot/releases/tag/3.5.10 https://pypi.org/project/Red-DiscordBot/3.5.10/
| Affected Software | Affected Version | How to fix |
|---|---|---|
| pip/Red-DiscordBot | >=3.5.0<3.5.10 | 3.5.10 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://github.com/Cog-Creators/Red-DiscordBot/security/advisories/GHSA-5jq8-q6rj-9gq4
- https://github.com/Cog-Creators/Red-DiscordBot/pull/6398
- https://github.com/Cog-Creators/Red-DiscordBot/commit/0b0b23b9717b40ed4f8715720b199417c8e89750
- https://nvd.nist.gov/vuln/detail/CVE-2024-39905
- https://github.com/advisories/GHSA-5jq8-q6rj-9gq4 (Advisory)
Frequently Asked Questions
What is the severity of GHSA-5jq8-q6rj-9gq4?
GHSA-5jq8-q6rj-9gq4 is classified as a moderate severity vulnerability affecting the Red-DiscordBot.
How do I fix GHSA-5jq8-q6rj-9gq4?
To fix GHSA-5jq8-q6rj-9gq4, upgrade your Red-DiscordBot to version 3.5.11 or later.
Who is affected by GHSA-5jq8-q6rj-9gq4?
GHSA-5jq8-q6rj-9gq4 affects users of Red-DiscordBot version 3.5.0 to 3.5.10 using third-party cogs.
What causes GHSA-5jq8-q6rj-9gq4?
GHSA-5jq8-q6rj-9gq4 is caused by a bug in the Red's Core API related to insufficient permission checks.
What can exploit GHSA-5jq8-q6rj-9gq4?
The vulnerability GHSA-5jq8-q6rj-9gq4 can be exploited when a user gains unauthorized access to commands by leveraging flawed permission checks.
- agent/severity
- agent/weakness
- agent/softwarecombine
- agent/type
- agent/first-publish-date
- agent/description
- agent/event
- agent/references
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-5jq8-q6rj-9gq4
- alias/CVE-2024-39905
- agent/software-canonical-lookup
- agent/last-modified-date
- collector/github-advisory
- agent/trending
- agent/tags
- agent/source
- package-manager/pip