# CVE-2006-4832: Memory corruption in n/a

> Remote attackers can cause denial of service or execute arbitrary code via a buffer overflow in the telnet service using a long username.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3x99-g65w-pxrx

## What is CVE-2006-4832?

CVE-2006-4832 is a high-severity memory corruption vulnerability in n/a, published on 15 Sep 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the telnet service in Verso NetPerformer FRAD ACT SDM-95xx 7.xx (R1) and earlier, SDM-93xx 10.x.x (R2) and earlier, and SDM-92xx 9.x.x (R1) and earlier allows remote attackers to cause a denial of service (reboot) and possibly execute arbitrary code via a long username.

## Which versions are affected by CVE-2006-4832?

It affects 1 product.


Products: Verso Netperformer Frame Relay Access Device Act.

## How do I fix CVE-2006-4832?

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

## Is CVE-2006-4832 being exploited?

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

Public exploit code:

- Verso NetPerformer Frame Relay Access Device - Telnet Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-4833](https://insights.sbomify.com/CVE-2006-4833/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4832 and fix it if it is affected.

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

## Sources

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

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