CVE-2004-1472
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 · uneditedSymantec Enterprise Firewall/VPN Appliances 100, 200, and 200R running firmware before 1.63 allow remote attackers to cause a denial of service (device freeze) via a fast UDP port scan on the WAN interface.
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 confidenceA denial of service vulnerability in Symantec Enterprise Firewall/VPN Appliances 100, 200, and 200R allows remote attackers to freeze the device by performing a fast UDP port scan on the WAN interface. The issue affects firmware versions prior to 1.63.
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 dataall versionsall versionsall versions= 320= 360= 360rall versionsall versionsall versionsall versionsCVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Identify the appliance modelLocate the physical device label or log into the device admin interface to confirm the exact model number (e.g., Symantec Firewall VPN Appliance 100, 200, 200R, or one of the listed Gateway Security or Nexland models)Affected if The model matches one of the products listed in the affected products and versions
-
Check the firmware versionAccess the device administrative interface or use the command-line interface to retrieve the current firmware version. Compare this version number to 1.63Affected if The installed firmware version is lower than 1.63 (or the version cannot be determined and the device is an affected model)
-
Verify WAN interface exposureDetermine whether the WAN interface of the device is directly accessible from untrusted external networks (such as the internet)Affected if The WAN interface is reachable from external networks and an attacker could perform a UDP port scan against it
-
Confirm UDP port scan accessibilityReview firewall or network filtering rules to confirm that UDP traffic to the WAN interface is permitted and not blocked by upstream security devicesAffected if UDP traffic to the WAN interface is allowed and the device is directly reachable from an untrusted network
The environment is affected if the device is a Symantec Firewall VPN Appliance 100, 200, or 200R (or one of the other listed models) running firmware prior to version 1.63 with an exposed WAN interface reachable for a UDP port scan.
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 dataUpgrade the appliance firmware to version 1.63 or later. As a compensating control, implement rate-limiting or IDS/IPS filtering on the WAN interface to detect and block rapid UDP port scans.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-1472 — 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-2004-1472 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