# CVE-2007-3638: Memory corruption in n/a

> A buffer overflow in Yahoo! Messenger allows remote attackers with address book access to execute arbitrary code via user-assisted vectors.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7r88-6fh6-rqh5

## What is CVE-2007-3638?

CVE-2007-3638 is a medium-severity memory corruption vulnerability in n/a, published on 10 Jul 2007. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in Yahoo! Messenger 8.1 allows user-assisted remote authenticated users, who are listed in an address book, to execute arbitrary code via unspecified vectors, aka ZD-00000005.  NOTE: this information is based upon a vague advisory by a vulnerability information sales organization that does not coordinate with vendors or release actionable advisories. A CVE has been assigned for tracking purposes, but duplicates with other CVEs are difficult to determine.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Yahoo Messenger.

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

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

## Is CVE-2007-3638 being exploited?

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

Public exploit code:

- Yahoo! Messenger 8.1 - Address Book Remote Buffer Overflow (exploitdb)

## 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-3638 and fix it if it is affected.

What it is: CVE-2007-3638 is a medium-severity memory corruption vulnerability in n/a, published on 10 Jul 2007. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-3638 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-2007-3638/ (Markdown: https://insights.sbomify.com/CVE-2007-3638/index.md)
```

## Sources

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

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