# CVE-2006-5563: Null dereference in n/a

> Remote attackers can crash Yahoo! Messenger via a crafted room name in a conference invite, requiring user acceptance.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **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:** 27 Oct 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8vmh-6cgm-cw63

## What is CVE-2006-5563?

CVE-2006-5563 is a medium-severity vulnerability in n/a, published on 27 Oct 2006. 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

Unspecified vulnerability in Yahoo! Messenger (Service 18) before 8.1.0.195 allows remote attackers to cause a denial of service (NULL dereference and application crash) via a crafted room name in a Conference Invite.  NOTE: the provenance of this information is unknown; the details are obtained from third party information.

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

It affects 1 product.


Products: Yahoo Messenger.

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

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

## Is CVE-2006-5563 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-7216](https://insights.sbomify.com/CVE-2014-7216/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-4515](https://insights.sbomify.com/CVE-2007-4515/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-4391](https://insights.sbomify.com/CVE-2007-4391/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-3147](https://insights.sbomify.com/CVE-2007-3147/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-3148](https://insights.sbomify.com/CVE-2007-3148/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5563 is a medium-severity vulnerability in n/a, published on 27 Oct 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-5563 in the wild and no public exploit code.

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-5563/ (Markdown: https://insights.sbomify.com/CVE-2006-5563/index.md)
```

## Sources

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

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