# CVE-2005-1468: Multiple unknown vulnerabilities in the (1) WSP, (2) Q.931, (3) H.245, (4) KINK, (5) MGCP, (6) RPC, (7) SMBMailslot, and (8) SMB NETLOGON di


- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 5 May 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7x4c-h27p-4w5g

## What is CVE-2005-1468?

CVE-2005-1468 is a medium-severity vulnerability in Ethereal Group Ethereal, published on 5 May 2005. 

### Official description

Multiple unknown vulnerabilities in the (1) WSP, (2) Q.931, (3) H.245, (4) KINK, (5) MGCP, (6) RPC, (7) SMBMailslot, and (8) SMB NETLOGON dissectors in Ethereal before 0.10.11 allow remote attackers to cause a denial of service (crash) via unknown vectors that lead to a null dereference.

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

It affects 1 product.


Products: Ethereal Group Ethereal.

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

Upgrade to a fixed version.

## Is CVE-2005-1468 being exploited?

There is no known exploitation of CVE-2005-1468 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-1468 and fix it if it is affected.

What it is: CVE-2005-1468 is a medium-severity vulnerability in Ethereal Group Ethereal, published on 5 May 2005. 
Exploitation: There is no known exploitation of CVE-2005-1468 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-1468/ (Markdown: https://insights.sbomify.com/CVE-2005-1468/index.md)
```

## Sources

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

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