# CVE-2021-29501: Remote code execution in ticketer


- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 May 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-r2cf-49r7-pfj7

## What is CVE-2021-29501?

CVE-2021-29501 is a high-severity vulnerability in Dav-Git Dav-Cogs, published on 10 May 2021. 

### Official description

Ticketer is a command based ticket system cog (plugin) for the red discord bot. A vulnerability allowing discord users to expose sensitive information has been found in the Ticketer cog. Please upgrade to version 1.0.1 as soon as possible. As a workaround users may unload the ticketer cog to disable the exploitable code.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2021-29501?

It affects 1 product.


Products: Dav-Cogs Project Dav-Cogs.

## How do I fix CVE-2021-29501?

No fix has been published for CVE-2021-29501 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-29501 being exploited?

There is no known exploitation of CVE-2021-29501 in the wild and no public exploit code.

## Other vulnerabilities in Dav-Git Dav-Cogs

- [CVE-2021-32646](https://insights.sbomify.com/CVE-2021-32646/): Escalation of permissions in roomer (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-29501 and fix it if it is affected.

What it is: CVE-2021-29501 is a high-severity vulnerability in Dav-Git Dav-Cogs, published on 10 May 2021. 
Exploitation: There is no known exploitation of CVE-2021-29501 in the wild and no public exploit code.

Affected product: Dav-Git Dav-Cogs. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-29501/ (Markdown: https://insights.sbomify.com/CVE-2021-29501/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-29501
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-29501
- OSV: https://osv.dev/vulnerability/CVE-2021-29501

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-29501/
Summaries are generated and may contain mistakes; the official description above is the record.