CVE-2000-0339
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 · uneditedZoneAlarm 2.1.10 and earlier does not filter UDP packets with a source port of 67, which allows remote attackers to bypass the firewall rules.
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 confidenceZoneAlarm personal firewall versions 2.1.10 and earlier fail to filter incoming UDP packets with source port 67 (the DHCP/bootp server port). This allows remote attackers to bypass firewall protection by sending malicious UDP traffic on port 67, which the firewall incorrectly permits as incoming traffic.
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<= 2.2.10CVSS 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.
-
Verify ZoneAlarm installationCheck for ZoneAlarm installation by looking for Zone Labs or ZoneAlarm program files in Program Files directory, or check Add/Remove Programs for ZoneAlarm entryAffected if ZoneAlarm is not installed on the system
-
Determine installed ZoneAlarm versionOpen ZoneAlarm interface and navigate to About/Version information, or check the Windows registry under HKLM\Software\Zone Labs\ZoneAlarm for the Version valueAffected if Installed version is 2.1.10 or earlier, or any version <= 2.2.10 per the affected product list
-
Check UDP port 67 inbound rule configurationIn ZoneAlarm main interface, go to Security > Firewall > Advanced > Custom and verify the inbound UDP rules, or check if there is an explicit allow rule for incoming UDP traffic on source port 67 from internet/untrusted zonesAffected if The firewall allows incoming UDP packets with source port 67 from external/untrusted sources
-
Test UDP port 67 filtering behaviorSend a test UDP packet to the protected machine on destination port (any) with source port set to 67, and verify if ZoneAlarm logs or blocks this traffic in the firewall logsAffected if UDP packets with source port 67 are permitted through the firewall without blocking or alerting
A system is affected if it runs ZoneAlarm version 2.1.10 or earlier (or <= 2.2.10) and the firewall permits incoming UDP packets from source port 67, allowing potential bypass of firewall protection.
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 ZoneAlarm to a version newer than 2.1.10. For legacy systems that cannot upgrade, consider network-level filtering to block untrusted UDP/67 inbound traffic.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0339 — 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-2000-0339 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