CVE-2004-0612
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 Mobile Code filter in ZoneAlarm Pro 5.0.590.015 does not filter mobile code within an SSL encrypted session, which could allow remote attackers to bypass the mobile code filtering. NOTE: it has been disputed by the vendor that this behavior is required by the SSL specification.
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 · moderate confidenceThe ZoneAlarm Pro 5.0.590.015 mobile code filter fails to inspect SSL-encrypted sessions for mobile code (Java applets, ActiveX, etc.), allowing malicious mobile code to bypass filtering when transported through encrypted channels.
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= 5.0.590.015CVSS 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
- High
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:H/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 Pro installationCheck if ZoneAlarm Pro is installed on the system by reviewing installed programs in Control Panel > Programs and Features, or checking for ZoneAlarm Pro in the system trayAffected if ZoneAlarm Pro is not installed, the system is not affected by this specific CVE
-
Confirm exact version numberOpen ZoneAlarm Pro interface and navigate to About/Version information, or check the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Zone Labs\ZoneAlarm Pro for the Version valueAffected if Version is exactly 5.0.590.015, the system is affected
-
Verify mobile code filter is enabledIn ZoneAlarm Pro, navigate to Program Control > Mobile Code (or similar mobile code filtering settings) and confirm the filter is turned onAffected if Mobile code filtering is disabled, the vulnerability cannot be exploited even on the affected version
-
Check if SSL inspection is configuredIn ZoneAlarm Pro settings, look for SSL inspection, HTTPS inspection, or encrypted session filtering options under the mobile code or firewall settingsAffected if SSL-encrypted sessions are not being inspected while mobile code filtering is enabled, the bypass vulnerability is present
The system is affected only if ZoneAlarm Pro version 5.0.590.015 is installed with mobile code filtering enabled and SSL-encrypted sessions are not being inspected for mobile code.
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 to a current version of ZoneAlarm or implement alternative security controls that can inspect SSL traffic for mobile code threats while maintaining the SSL inspection capability.
- Consultation2.0 h
- Implementation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-0612 — 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-0612 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