# CVE-2007-0825: Denial of service in n/a

> A remote server can cause a denial of service in FlashFXP by sending a deeply nested directory structure in response to a PWD command.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8x2v-m9rp-648r

## What is CVE-2007-0825?

CVE-2007-0825 is a high-severity denial of service vulnerability in n/a, published on 7 Feb 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

FlashFXP 3.4.0 build 1145 allows remote servers to cause a denial of service (CPU consumption) via a response to a PWD command that contains a long string with deeply nested directory structure, possibly due to a buffer overflow.

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

It affects 1 product.


Products: Flashfxp Flashfxp.

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

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

## Is CVE-2007-0825 being exploited?

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

Public exploit code:

- FlashFXP 3.4.0 build 1145 - Remote Buffer Overflow (Denial of Service) (PoC) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-4992](https://insights.sbomify.com/CVE-2012-4992/): Memory corruption in n/a (critical 9.0)
- [CVE-2003-1483](https://insights.sbomify.com/CVE-2003-1483/): Weak cryptography in n/a (medium 6.4)
- [CVE-2002-1939](https://insights.sbomify.com/CVE-2002-1939/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-0825 is a high-severity denial of service vulnerability in n/a, published on 7 Feb 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-0825 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-0825/ (Markdown: https://insights.sbomify.com/CVE-2007-0825/index.md)
```

## Sources

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

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