dbcve.org
Discord ReconApplication · Discord

CVE-2021-29465

CRITICAL · 9.8 CVSS v3.1 Published 2021-04-22
Fix available
A fix is available. Upgrade to 0.0.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Discord-Recon is a bot for the Discord chat service. Versions of Discord-Recon 0.0.3 and prior contain a vulnerability in which a remote attacker is able to overwrite any file on the system with the command results. This can result in remote code execution when the user overwrite important files on the system. As a workaround, bot maintainers can edit their `setting.py` file then add `<` and `>` into the `RCE` variable inside of it to fix the issue without an update. The vulnerability is patched in version 0.0.4.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Discord-Recon bot versions 0.0.3 and prior contain a file overwrite vulnerability allowing remote attackers to write arbitrary content to any file on the system. This can be leveraged for remote code execution by overwriting critical system files. The vulnerability stems from unsanitized input being used in file write operations.

MitigationUpgrade to Discord-Recon version 0.0.4 or later, or apply the workaround by adding '<' and '>' characters to the RCE variable in the setting.py file to prevent arbitrary file writes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Discord ReconApplication
Affected:< 0.0.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Discord-Recon is installed
    Run 'pip show discord-recon' or 'pip list | grep -i discord' to see if the package is installed
    Affected if The package is not found in pip list
  2. Verify the installed version number
    Examine the version field from pip show output, or check the __version__ attribute in the source code if available
    Affected if Version is 0.0.3 or lower, or version cannot be determined (likely vulnerable)
  3. Inspect the source code for vulnerable file write logic
    Locate the discord-recon source (typically in site-packages/discord_recon/) and search for file write operations using 'open(' or 'write' functions that lack input sanitization
    Affected if Code contains open() write operations without sanitization checks on user-controlled input
  4. Check for exposure to untrusted input
    Review the bot's command handlers or web interfaces that accept user input and pass it to file operations
    Affected if User-supplied data can reach file write functions without validation

You are affected if Discord-Recon version 0.0.3 or prior is installed and untrusted input can reach file write operations without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.0.4 or later
Fixed in 0.0.4
Interim mitigation

Upgrade to Discord-Recon version 0.0.4 or later, or apply the workaround by adding '<' and '>' characters to the RCE variable in the setting.py file to prevent arbitrary file writes.

Recommended fix High confidence

0.0.4

  1. Update Discord-Recon to version 0.0.4 or later by pulling the latest release from the repository
  2. Verify the update was successfully applied by checking the installed version
  3. Restart the Discord bot service to load the updated code
  4. Test that the bot functionality remains intact after the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Discord Recon Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-29465 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-29465 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data