LiveActive security incident?Get immediate response
CVE Record

CVE-2004-0444: Multiple vulnerabilities in SYMDNS.SYS for Symantec Norton Internet Security and Professional 2002 through...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2004-0444 covers multiple flaws in Symantec firewall-related products from 2002 to 2004. A remote attacker could crash affected systems or potentially run code by sending malformed NBNS or DNS responses. The business concern is legacy endpoint or firewall software still present on old workstations, servers, or embedded builds. Exposure is most plausible in legacy environments running affected Symantec Norton Internet Security, Norton Personal Firewall, Norton AntiSpam, Client Firewall, or Client Security versions listed in the CVE. Modern environments are unlikely to run these versions, but old gold images, labs, and unmanaged endpoints should be checked. Prioritize discovery over emergency response. This is a serious remote code execution and denial-of-service issue, but the affected products are very old and no active exploitation is cited in the provided sources. Any remaining installations should be removed, upgraded, or isolated. Mitigation focus: Identify any affected Symantec products and versions listed in the CVE record.; Check Symantec’s 2004 advisory for product-specific update or mitigation guidance.; Retire or replace unsupported 2002-2004 Symantec firewall/security software..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2004-0444 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.