cve.bz

CVE-2004-0444 symantec

no score yetEPSS 13%Fix available

symantec: no CVSS score yet. EPSS 13% estimated probability of exploitation activity in the next 30 days.

On this page
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.
EPSS
13% (unchanged from 13% a week ago; 13% 30 days ago) estimated probability of exploitation activity in the next 30 days; 96th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2004-0444 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2004-0444?via=ask-ai-copy and https://cve.bz/cve/CVE-2004-0444?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2004-0444 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
symantec:client_firewall5.01
symantec:client_firewall5.1.1
symantec:client_security1.0
symantec:client_security1.1
symantec:client_security1.2
symantec:client_security1.3
symantec:client_security1.4
symantec:client_security1.5
symantec:client_security1.6
symantec:client_security1.7
symantec:client_security1.8
symantec:client_security1.9
symantec:client_security2.0
symantec:norton_antispam2004
symantec:norton_internet_security2002
symantec:norton_internet_security2003
symantec:norton_internet_security2004
symantec:norton_personal_firewall2002
symantec:norton_personal_firewall2003
symantec:norton_personal_firewall2004

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

References

Check your stackJSON