# CVE-2005-3651: Memory corruption in n/a

> Remote attackers can execute arbitrary code via crafted OSPF packets due to a stack-based buffer overflow in the Ethereal network analyzer.

- **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:** Yes
- **Published:** 10 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-920-1, GHSA-5c39-44xr-89vv

## What is CVE-2005-3651?

CVE-2005-3651 is a high-severity memory corruption vulnerability in Ethereal Group Ethereal, published on 10 Dec 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow in the dissect_ospf_v3_address_prefix function in the OSPF protocol dissector in Ethereal 0.10.12, and possibly other versions, allows remote attackers to execute arbitrary code via crafted packets.

## Which versions are affected by CVE-2005-3651?

It affects 1 product.


Products: Ethereal Group Ethereal.

## How do I fix CVE-2005-3651?

Upgrade to a fixed version.

## Is CVE-2005-3651 being exploited?

There is no known exploitation of CVE-2005-3651 in the wild and no public exploit code.

## Other vulnerabilities in Ethereal Group Ethereal

- [CVE-2006-3628](https://insights.sbomify.com/CVE-2006-3628/): Other in n/a (critical 10.0)
- [CVE-2006-3632](https://insights.sbomify.com/CVE-2006-3632/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-1932](https://insights.sbomify.com/CVE-2006-1932/): Integer overflow in n/a (critical 10.0)
- [CVE-2005-3184](https://insights.sbomify.com/CVE-2005-3184/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0507](https://insights.sbomify.com/CVE-2004-0507/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-3651 and fix it if it is affected.

What it is: CVE-2005-3651 is a high-severity memory corruption vulnerability in Ethereal Group Ethereal, published on 10 Dec 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-3651 in the wild and no public exploit code.

Affected product: Ethereal Group Ethereal. 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-2005-3651/ (Markdown: https://insights.sbomify.com/CVE-2005-3651/index.md)
```

## Sources

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

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