# CVE-2005-2390: Other in n/a

> Attackers can cause denial of service or read sensitive information via format string flaws in ProFTPD's shutdown message or SQLShowInfo directive.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-795-2, GHSA-mxr8-fr7q-582m

## What is CVE-2005-2390?

CVE-2005-2390 is a medium-severity vulnerability in n/a, published on 27 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple format string vulnerabilities in ProFTPD before 1.3.0rc2 allow attackers to cause a denial of service or obtain sensitive information via (1) certain inputs to the shutdown message from ftpshut, or (2) the SQLShowInfo mod_sql directive.

## Which versions are affected by CVE-2005-2390?

It affects 1 product.


Products: Proftpd Project Proftpd.

## How do I fix CVE-2005-2390?

Upgrade to a fixed version.

## Is CVE-2005-2390 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-5815](https://insights.sbomify.com/CVE-2006-5815/): Memory corruption in n/a (critical 10.0)
- [CVE-2003-0500](https://insights.sbomify.com/CVE-2003-0500/): SQL injection in n/a (critical 10.0)
- [CVE-1999-0911](https://insights.sbomify.com/CVE-1999-0911/): Memory corruption in n/a (critical 10.0)
- [CVE-2003-0831](https://insights.sbomify.com/CVE-2003-0831/): Memory corruption in n/a (critical 9.0)
- [CVE-2009-0542](https://insights.sbomify.com/CVE-2009-0542/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2390 and fix it if it is affected.

What it is: CVE-2005-2390 is a medium-severity vulnerability in n/a, published on 27 Jul 2005. 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-2005-2390 in the wild and no public exploit code.

Affected product: n/a. 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-2005-2390/ (Markdown: https://insights.sbomify.com/CVE-2005-2390/index.md)
```

## Sources

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

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