Patchfirst
CVE-2020-15140 High · 8.2 EPSS 1.2%

Remote Code Execution in Red Discord Bot

Cog-Creators · Red-DiscordBot

Official description · CVE.org

In Red Discord Bot before version 3.3.11, a RCE exploit has been discovered in the Trivia module: this exploit allows Discord users with specifically crafted usernames to inject code into the Trivia module's leaderboard command. By abusing this exploit, it's possible to perform destructive actions and/or access sensitive information. This critical exploit has been fixed on version 3.3.11.

Breakdown
19.1 / 100
Exploited
Not confirmed
Reports
0
Tactics
3/15

How an attack unfolds

Based on mappings. Select a step to see the evidence.
  1. How attackers get in

  2. What they do

Disclosed on 21 Aug 2020. No public exploit code or confirmed exploitation is recorded.

4 fixes in Red-DiscordBot over 4 years. The latest fix listed for Red-DiscordBot is 3.5.10.

Fixes in Red-DiscordBotPyPI package, by fixed version. Earlier and later fixes in the same package, not necessarily the same bug.

  1. 3.3.11CVE-2020-1514021 Aug 2020
  2. 3.3.12CVE-2020-1514721 Aug 2020
  3. 3.4.1CVE-2020-1527828 Oct 2020
  4. 3.5.10CVE-2024-3990511 Jul 2024Latest listed

techniques

2 , grouped by in kill-chain order 2

Initial AccessTA0001

External Remote Services T1133 also Persistence
MITRE CTID mapping of the CVE · how it is exploited

ExecutionTA0002

MITRE CTID mapping of the CVE · primary impact

Detection

0 rules for this CVE · 115 general rules for its techniques

Rules for this CVE

0 that reference CVE-2020-15140 directly.

CVE-specific rules are not available in this build. Search SigmaHQ ↗

Sigma rules © SigmaHQ, Detection Rule License 1.1; linked, not reproduced.

Am I affected? What do I upgrade to?

From GitHub Security Advisories and OSV

1 package in 1 ecosystem. Main package: Red-DiscordBot.

Upgrade to 3.3.12 or later

Fixes this CVE and 1 other known vulnerability in this package (CVE-2020-15147).

pippip install "Red-DiscordBot>=3.3.12"

First fixed in 3.3.11 for CVE-2020-15140.

Affected versions

If you runUpgrade to
All versions before 3.3.113.3.12first fix for this CVE: 3.3.11

“Up to” means the second version is the fix and is not affected.

Check your lockfile against all CVEs

What security researchers reported

Not named in any threat report yet

References

2 links, grouped by NVD tag
↑ ↓ chooseEnter openEsc close