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

> Remote attackers can execute arbitrary code via buffer overflows in FSD server software, requiring low privileges for one vector.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-x24x-32q2-mhm4

## What is CVE-2007-5256?

CVE-2007-5256 is a high-severity memory corruption vulnerability in n/a, published on 6 Oct 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple stack-based buffer overflows in FSD 2.052 d9 and earlier, and FSFDT FSD 3.000 d9 and earlier, allow (1) remote attackers to execute arbitrary code via a long HELP command on TCP port 3010 to the sysuser::exechelp function in sysuser.cc and (2) remote authenticated users to execute arbitrary code via long commands on TCP port 6809 to the servinterface::sendmulticast function in servinterface.cc, as demonstrated by a PIcallsign command.

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

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

It affects 1 product.


Products: Mcdu Fsd.

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

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

## Is CVE-2007-5256 being exploited?

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

Public exploit code:

- FSD 2.052/3.000 - 'sysuser.cc sysuser::exechelp' 'HELP' Remote Overflow (exploitdb)
- FSD 2.052/3.000 - 'servinterface.cc servinterface::sendmulticast' 'PIcallsign' Command Remote Overflow (exploitdb)
- FSFDT v3.000 d9 - 'HELP' Remote Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-5256 is a high-severity memory corruption vulnerability in n/a, published on 6 Oct 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-5256 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-5256/ (Markdown: https://insights.sbomify.com/CVE-2007-5256/index.md)
```

## Sources

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

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