Skip to content

Bots using py-cord as Discord API wrapper are vulnerable to shutdowns through remote code execution

High severity GitHub Reviewed Published Aug 16, 2022 in Pycord-Development/pycord • Updated Nov 22, 2024

Package

pip py-cord (pip)

Affected versions

= 2.0.0

Patched versions

2.0.1

Description

Impact

py-cord is a an API wrapper for Discord written in Python. Bots using py-cord version 2.0.0 are vulnerable to remote shutdown if they are added to the server with the application.commands scope without the bot scope. Currently, it appears that all public bots that use slash commands are affected.

Patches

This issue has been patched in version 2.0.1.

Workarounds

There are currently no recommended workarounds - please upgrade to a patched version.

References

Pycord-Development/pycord#1568

For more information

If you have any questions or comments about this advisory:

References

@BobDotCom BobDotCom published to Pycord-Development/pycord Aug 16, 2022
Published to the GitHub Advisory Database Aug 18, 2022
Reviewed Aug 18, 2022
Published by the National Vulnerability Database Aug 18, 2022
Last updated Nov 22, 2024

Severity

High

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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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:N/S:U/C:N/I:N/A:H

EPSS score

0.076%
(35th percentile)

Weaknesses

CVE ID

CVE-2022-36024

GHSA ID

GHSA-qmhj-m29v-gvmr

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.