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

> A remote FTP server can trigger a stack-based buffer overflow in W3Filer, causing a crash or potentially executing arbitrary code when a user uploads a file.

- **Severity:** High 7.1 (`AV:N/AC:M/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:** 3 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fgg3-cq2r-mqwx

## What is CVE-2007-3548?

CVE-2007-3548 is a high-severity memory corruption vulnerability in n/a, published on 3 Jul 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

Stack-based buffer overflow in W3Filer 2.1.3 allows remote FTP servers to cause a denial of service (application hang or crash) and possibly execute arbitrary code by sending a large banner to a client that is sending a file.

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

It affects 1 product.


Products: W3filer W3filer.

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

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

## Is CVE-2007-3548 being exploited?

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

Public exploit code:

- W3Filer 2.1.3 - Remote Stack Overflow (PoC) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-3548 is a high-severity memory corruption vulnerability in n/a, published on 3 Jul 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-3548 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-3548/ (Markdown: https://insights.sbomify.com/CVE-2007-3548/index.md)
```

## Sources

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

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