# CVE-2009-4629: Information disclosure in n/a

> Remote attackers can determine user network location via DNS prefetching in email clients when reading plain text messages.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **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:** 29 Jan 2010
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-vvr5-jq6q-h8jj

## What is CVE-2009-4629?

CVE-2009-4629 is a medium-severity vulnerability in Mozilla Seamonkey, published on 29 Jan 2010. 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

Mozilla Necko, as used in Thunderbird 3.0.1, SeaMonkey, and other applications, performs DNS prefetching even when the app type is APP_TYPE_MAIL or APP_TYPE_EDITOR, which makes it easier for remote attackers to determine the network location of the application's user by logging DNS requests, as demonstrated by DNS requests triggered by reading text/plain e-mail messages in Thunderbird.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2009-4629?

It affects 2 products.


Products: Mozilla Seamonkey, Mozilla Thunderbird.

## How do I fix CVE-2009-4629?

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

## Is CVE-2009-4629 being exploited?

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

## Other vulnerabilities in Mozilla Seamonkey

- [CVE-2008-4070](https://insights.sbomify.com/CVE-2008-4070/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-4571](https://insights.sbomify.com/CVE-2006-4571/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-2210](https://insights.sbomify.com/CVE-2009-2210/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-1282](https://insights.sbomify.com/CVE-2007-1282/): Integer overflow in n/a (critical 9.3)
- [CVE-2008-0304](https://insights.sbomify.com/CVE-2008-0304/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-4629 and fix it if it is affected.

What it is: CVE-2009-4629 is a medium-severity vulnerability in Mozilla Seamonkey, published on 29 Jan 2010. 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-2009-4629 in the wild and no public exploit code.

Affected product: Mozilla Seamonkey. 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-2009-4629/ (Markdown: https://insights.sbomify.com/CVE-2009-4629/index.md)
```

## Sources

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

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