# CVE-2007-5300: Memory corruption in n/a

> Remote attackers can crash the wzdftpd daemon via a stack-based buffer overflow in the login function, causing denial of service.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/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:** 9 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-1452-1, GHSA-hjg5-38g6-376g

## What is CVE-2007-5300?

CVE-2007-5300 is a medium-severity memory corruption vulnerability in n/a, published on 9 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Off-by-one error in the do_login_loop function in libwzd-core/wzd_login.c in wzdftpd 0.8.0, 0.8.2, and possibly other versions allows remote attackers to cause a denial of service (daemon crash) via a long USER command that triggers a stack-based buffer overflow.  NOTE: some of these details are obtained from third party information.

Weakness: CWE-189, CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2007-5300?

It affects 1 product.


Products: Wzdftpd Wzdftpd.

## How do I fix CVE-2007-5300?

Apply the vendor's patch.

## Is CVE-2007-5300 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-5300 exists.

Public exploit code:

- WzdFTPD 0.8.0 - 'USER' Remote Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-0428](https://insights.sbomify.com/CVE-2007-0428/): Null dereference in n/a (medium 5.0)
- [CVE-2003-0477](https://insights.sbomify.com/CVE-2003-0477/): Denial of service in n/a (medium 5.0)
- [CVE-2005-3081](https://insights.sbomify.com/CVE-2005-3081/): Command injection in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5300 and fix it if it is affected.

What it is: CVE-2007-5300 is a medium-severity memory corruption vulnerability in n/a, published on 9 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-5300 exists.

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-2007-5300/ (Markdown: https://insights.sbomify.com/CVE-2007-5300/index.md)
```

## Sources

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

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