CVE-2007-2730
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 · uneditedCheck Point ZoneAlarm Pro before 6.5.737.000 does not properly test for equivalence of process identifiers for certain Microsoft Windows API functions in the NT kernel 5.0 and greater, which allows local users to call these functions, and bypass firewall rules or gain privileges, via a modified identifier that is one, two, or three greater than the canonical identifier.
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 confidenceZoneAlarm Pro before 6.5.737.000 fails to properly validate process identifiers when enforcing firewall rules for Windows API functions on NT kernel 5.0+. Local attackers can bypass firewall rules or gain privileges by using a modified PID that is 1-3 higher than the canonical process ID, exploiting inadequate equivalence checking in the software.
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<= 6.1.744.001= 2.4.18.184= 2.3.6.81CVSS 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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
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.
-
Check if ZoneAlarm Pro is installedOpen Control Panel > Programs and Features, or check the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ZoneAlarmProAffected if ZoneAlarm Pro appears in installed programs or registry
-
Determine ZoneAlarm Pro versionRight-click the ZoneAlarm icon in the system tray and select 'About', or check the version in Add/Remove ProgramsAffected if Version number is 6.1.744.001 or lower
-
Check if Comodo Firewall Pro is installedOpen Control Panel > Programs and Features, or check for COMODO Firewall in the system trayAffected if Comodo Firewall Pro 2.4.18.184 is installed
-
Check if Comodo Personal Firewall is installedOpen Control Panel > Programs and Features, or check for Comodo in the system trayAffected if Comodo Personal Firewall version 2.3.6.81 is installed
-
Verify firewall protection is activeCheck the ZoneAlarm or Comodo interface to confirm the firewall component is enabled and runningAffected if The firewall software is running with the firewall protection enabled
Your environment is affected if ZoneAlarm Pro version 6.1.744.001 or lower, Comodo Firewall Pro 2.4.18.184, or Comodo Personal Firewall 2.3.6.81 is installed and the firewall is active.
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 Pro to version 6.5.737.000 or later, which contains proper process identifier validation. As a local privilege escalation/firewall bypass vulnerability, prioritize patching affected endpoints immediately.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2730 — 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-2007-2730 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