Vulnerability in red-discordbot (CVE-2020-15147)
Summary
Vulnerability in red-discordbot (CVE-2020-15147). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 3.3.12 or later.
Original description
The description as published by the source.
Impact
A RCE exploit has been discovered in the Streams module: this exploit allows Discord users with specifically crafted "going live" messages to inject code into the Streams module's going live message. By abusing this exploit, it's possible to perform destructive actions and/or access sensitive information.
Patches
This critical exploit has been fixed on version 3.3.12 & 3.4.
Workarounds
Unloading the Streams module with unload streams can render this exploit not accessible. We still highly recommend updating to 3.3.12 or 3.4 to completely patch this issue.
References
For more information
If you have any questions or comments about this advisory:
- Open an issue in Cog-Creators/Red-DiscordBot
- Over on our Discord server
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2020-15147 has been found in red-discordbot.
Successful exploitation can lead to full system takeover.
What to do: upgrade red-discordbot to 3.3.12 or later.
If unsure, ask your IT team or search "red-discordbot CVE-2020-15147" on the vendor's site.
CVE-2020-15147 (red-discordbot) — CWE-74
Attack vector: remote (network-reachable) / no user interaction
Patched: 3.3.12 — apply immediately
Workaround: Unloading the Streams module with unload streams can render this exploit not accessible.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-74) exists in red-discordbot.
Check the vendor advisory for the affected versions of red-discordbot.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 3.3.12.
Workaround: Unloading the Streams module with unload streams can render this exploit not accessible.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'red-discordbot' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'red-discordbot' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
red-discordbotを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Unloading the Streams module with ``unload streams`` can render this exploit not accessible.パッチが適用されるまでの応急処置として、Unloading the Streams module with
unload streamscan render this exploit not accessible. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade red-discordbot to 3.3.12ステージング環境で 3.3.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com