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

> Remote attackers can cause a denial of service via infinite loop in the SYMDNS.SYS driver by sending a malicious DNS response.

- **Severity:** Low 2.6 (`AV:N/AC:H/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:** 20 May 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-6p52-7j69-f67w

## What is CVE-2004-0445?

CVE-2004-0445 is a low-severity denial of service vulnerability in n/a, published on 20 May 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The SYMDNS.SYS driver in Symantec Norton Internet Security and Professional 2002 through 2004, Norton Personal Firewall 2002 through 2004, Norton AntiSpam 2004, Client Firewall 5.01 and 5.1.1, and Client Security 1.0 through 2.0 allows remote attackers to cause a denial of service (CPU consumption from infinite loop) via a DNS response with a compressed name pointer that points to itself.

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

It affects 5 products.


Products: Symantec Client Firewall, Symantec Client Security, Symantec Norton Antispam, Symantec Norton Internet Security, Symantec Norton Personal Firewall.

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

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

## Is CVE-2004-0445 being exploited?

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

Public exploit code:

- Symantec Multiple Firewall - DNS Response Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2004-0444](https://insights.sbomify.com/CVE-2004-0444/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0375](https://insights.sbomify.com/CVE-2004-0375/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0445 is a low-severity denial of service vulnerability in n/a, published on 20 May 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-0445 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-2004-0445/ (Markdown: https://insights.sbomify.com/CVE-2004-0445/index.md)
```

## Sources

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

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