# CVE-2004-1768: Denial of service in n/a

> Remote attackers can crash Symantec Brightmail AntiSpam by sending messages with the unsupported ISO-8859-10 character set.

- **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:** 10 Mar 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-8gp2-v2vm-xr7x

## What is CVE-2004-1768?

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

### Official description

The character converters in the Spamhunter and Language ID modules for Symantec Brightmail AntiSpam 6.0.1 before patch 132 allow remote attackers to cause a denial of service (crash) via messages with the ISO-8859-10 character set, which is not recognized by the converters.

## Which versions are affected by CVE-2004-1768?

It affects 1 product.


Products: Symantec Brightmail Antispam.

## How do I fix CVE-2004-1768?

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

## Is CVE-2004-1768 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-4013](https://insights.sbomify.com/CVE-2006-4013/): Path traversal in n/a (high 7.6)
- [CVE-2005-1867](https://insights.sbomify.com/CVE-2005-1867/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2006-4014](https://insights.sbomify.com/CVE-2006-4014/): Denial of service in n/a (medium 5.0)
- [CVE-2005-4695](https://insights.sbomify.com/CVE-2005-4695/): Denial of service in n/a (medium 5.0)
- [CVE-2004-0671](https://insights.sbomify.com/CVE-2004-0671/): Missing authorization in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1768 and fix it if it is affected.

What it is: CVE-2004-1768 is a medium-severity denial of service vulnerability in n/a, published on 10 Mar 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-2004-1768 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-2004-1768/ (Markdown: https://insights.sbomify.com/CVE-2004-1768/index.md)
```

## Sources

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

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