CVE-2002-1779
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe "block fragmented IP Packets" option in Symantec Norton Personal Firewall 2002 (NPW) does not properly protect against certain attacks on Windows vulnerabilities such as jolt2 (CVE-2000-0305).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSymantec Norton Personal Firewall 2002 includes a 'block fragmented IP Packets' feature intended to mitigate fragmentation-based denial of service attacks, but the protection mechanism is flawed and fails to properly filter or block malicious fragmented packets like those used by the jolt2 exploit (CVE-2000-0305), allowing attackers to bypass the firewall's defense.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2002CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Norton Personal Firewall 2002 is installedCheck the installed programs list or look for Norton Personal Firewall 2002 in Add/Remove Programs (Windows XP/2000 era). Also check for Norton icon in system tray.Affected if The product is not installed or a different Norton product is installed (not version 2002)
-
Verify the 'block fragmented IP packets' feature is enabledOpen Norton Personal Firewall 2002 settings, navigate to the 'Advanced' or 'Security' settings section, and locate the 'Block fragmented IP packets' option. Check if it is checked/enabled.Affected if The feature is enabled but the CVE states the protection is flawed and fails to properly filter malicious fragmented packets when this setting is active
-
Confirm the firewall is actively filtering trafficVerify Norton Personal Firewall 2002 service is running (npf.exe or similar process in Task Manager). Ensure the firewall is not in 'disabled' or 'allow all' mode.Affected if The firewall service is not running or is set to permit all traffic by default
-
Test for fragmentation vulnerabilityUse a network testing tool to send fragmented ICMP packets (similar to jolt2 style) toward the protected system and observe if they reach the target host despite the 'block fragmented packets' setting being enabled.Affected if Fragmented packets reach the target system when the 'block fragmented IP packets' feature is supposedly enabled
The system is affected if Norton Personal Firewall 2002 is installed with the 'block fragmented IP packets' feature enabled, as the flaw allows malicious fragmented packets to bypass the firewall's defense.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataSince Norton Personal Firewall 2002 is an unsupported legacy product from 2002, the recommended remediation is to migrate to a modern, supported firewall solution or upgrade to current Norton security products that address this vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-1779 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2002-1779 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data