# CVE-2005-3678: Denial of service in n/a

> Remote attackers can cause a denial of service in Google Talk via email with a blank sender when email notifications are enabled.

- **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:** Not needed
- **Fix available:** No
- **Published:** 18 Nov 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3rw6-hwqf-q8xr

## What is CVE-2005-3678?

CVE-2005-3678 is a medium-severity denial of service vulnerability in n/a, published on 18 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Google Talk before 1.0.0.76, with email notification enabled, allows remote attackers to cause a denial of service (connection reset) via email with a blank sender.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Google Talk.

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

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

## Is CVE-2005-3678 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-3899](https://insights.sbomify.com/CVE-2005-3899/): Denial of service in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-3678 and fix it if it is affected.

What it is: CVE-2005-3678 is a medium-severity denial of service vulnerability in n/a, published on 18 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-3678 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-2005-3678/ (Markdown: https://insights.sbomify.com/CVE-2005-3678/index.md)
```

## Sources

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

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