# CVE-2007-0868: Denial of service in n/a

> Remote attackers can cause a denial of service in Yahoo! Messenger via unspecified vectors in the Chat Room functionality.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 9 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rjw6-27r7-qwj8

## What is CVE-2007-0868?

CVE-2007-0868 is a medium-severity denial of service vulnerability in n/a, published on 9 Feb 2007. It can be exploited over the network.

### Official description

Unspecified vulnerability in the Chat Room functionality in Yahoo! Messenger 8.1.0.239 and earlier allows remote attackers to cause a denial of service via unspecified vectors.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

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

It affects 1 product.


Products: Yahoo Messenger.

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

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

## Is CVE-2007-0868 being exploited?

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

What it is: CVE-2007-0868 is a medium-severity denial of service vulnerability in n/a, published on 9 Feb 2007. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2007-0868 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-2007-0868/ (Markdown: https://insights.sbomify.com/CVE-2007-0868/index.md)
```

## Sources

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

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