# CVE-2023-30621: OS command injection in Gipsy

> Attackers can execute arbitrary commands with root privileges via the ping command in the Gipsy Discord bot.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Apr 2023
- **Updated:** 4 Feb 2025
- **Also known as:** GHSA-6cw6-r8pg-j7wh

## What is CVE-2023-30621?

CVE-2023-30621 is a critical command injection vulnerability in Curiosity-org Gipsy, published on 21 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Gipsy is a multi-purpose discord bot which aim to be as modular and user-friendly as possible. In versions prior to 1.3 users can run command on the host machine with sudoer permission. The `!ping` command when provided with an IP or hostname used to run a bash `ping <IP>` without verification that the IP or hostname was legitimate. This command was executed with root permissions and may lead to arbitrary command injection on the host server. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2023-30621?

It affects 1 product.


Products: Gipsy Project Gipsy.

## How do I fix CVE-2023-30621?

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

## Is CVE-2023-30621 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-30621 and fix it if it is affected.

What it is: CVE-2023-30621 is a critical command injection vulnerability in Curiosity-org Gipsy, published on 21 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-30621 in the wild and no public exploit code.

Affected product: Curiosity-org Gipsy. 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-2023-30621/ (Markdown: https://insights.sbomify.com/CVE-2023-30621/index.md)
```

## Sources

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

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