Skip to content

Unauthenticated users can obtain any role via the !reaction_role command

High
YurBoiRene published GHSA-pg37-hhxv-79xh Dec 18, 2022

Package

No package listed

Affected versions

< ef6c54d370cf3900f53fa4bdd6ea51e999884689

Patched versions

ef6c54d370cf3900f53fa4bdd6ea51e999884689

Description

Impact

Unauthenticated users can obtain any role under the bot's top role by using the !reaction_role command. This will create a "React to this message to get role" message in the channel of the attacker's choice. Any role can be specified. Although the bot replies with a stern "Not authorized," it continues with the request happily. After the reaction role message is sent, the attacker can react to the message to obtain the role.

Note that the vulnerable command can be used by any user, and can even be used within DM.

Patches

ef6c54d

Workarounds

Remove OSUBot or demote OSUBot's role.

References

You can contact @YurBoiRene or @ndrewh

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
Changed
Confidentiality
None
Integrity
High
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:N/S:C/C:N/I:H/A:N

CVE ID

No known CVE

Weaknesses

Credits