# CVE-2004-0444: Memory corruption in n/a

> Remote attackers can execute arbitrary code or cause denial of service via buffer overflows in Symantec security software network components.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **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-7gq9-m389-5v2h

## What is CVE-2004-0444?

CVE-2004-0444 is a critical memory corruption 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

Multiple vulnerabilities in SYMDNS.SYS for 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 allow remote attackers to cause a denial of service or execute arbitrary code via (1) a manipulated length byte in the first-level decoding routine for NetBIOS Name Service (NBNS) that modifies an index variable and leads to a stack-based buffer overflow, (2) a heap-based corruption problem in an NBNS response that is missing certain RR fields, and (3) a stack-based buffer overflow in the DNS component via a Resource Record (RR) with a long canonical name (CNAME) field composed of many smaller components.

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

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-0444?

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

## Is CVE-2004-0444 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-0375](https://insights.sbomify.com/CVE-2004-0375/): Denial of service in n/a (medium 5.0)
- [CVE-2004-0445](https://insights.sbomify.com/CVE-2004-0445/): Denial of service in n/a (low 2.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0444 is a critical memory corruption 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: There is no known exploitation of CVE-2004-0444 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-0444/ (Markdown: https://insights.sbomify.com/CVE-2004-0444/index.md)
```

## Sources

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

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