CVE-2005-2932
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 · uneditedMultiple Check Point Zone Labs ZoneAlarm products before 7.0.362, including ZoneAlarm Security Suite 5.5.062.004 and 6.5.737, use insecure default permissions for critical files, which allows local users to gain privileges or bypass security controls.
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 products before version 7.0.362 contain insecure default file permissions on critical system files, allowing local unprivileged users to modify or replace these files. This enables local privilege escalation or bypass of security controls.
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<= 7.0.337.0= 5.5.062.004= 6.5.737CVSS 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.
-
Detect if ZoneAlarm is installedLook for ZoneAlarm in the list of installed programs via Control Panel > Programs and Features, or check for ZoneAlarm installation directories (typically in C:\Program Files\Zone Labs or C:\Program Files\CheckPoint)Affected if ZoneAlarm or Checkpoint ZoneAlarm Security Suite appears in installed programs
-
Identify the installed versionRight-click on the ZoneAlarm application in Programs and Features and select Properties, or look for version information in the ZoneAlarm program directory or help/about sectionAffected if A specific version number is displayed that can be compared to the affected ranges
-
Compare version to affected rangesMatch the installed version against these vulnerable versions: ZoneAlarm <= 7.0.337.0, ZoneAlarm Security Suite = 5.5.062.004 or = 6.5.737. For ZoneAlarm, any version 7.0.337.0 or lower is affected. For Security Suite, only versions 5.5.062.004 and 6.5.737 are listed as affected.Affected if The installed version falls within or below 7.0.337.0 for ZoneAlarm, or matches exactly 5.5.062.004 or 6.5.737 for ZoneAlarm Security Suite
-
Check file permissions on ZoneAlarm directoriesUse icacls or a file permission auditing tool to inspect permissions on the ZoneAlarm installation folder and critical system files that ZoneAlarm protects. Verify if standard user accounts have write or modify permissions to these locations.Affected if Unprivileged users have write, modify, or full control permissions on ZoneAlarm program files or protected system files
If ZoneAlarm or ZoneAlarm Security Suite is installed and the version is 7.0.337.0 or lower (or exactly 5.5.062.004/6.5.737 for Security Suite), and unprivileged users can modify ZoneAlarm-related files, the system is affected by this vulnerability.
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 version 7.0.362 or later to obtain the corrected default file permissions, or apply vendor-supplied patches that fix the permission issues.
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-2932 — 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-2005-2932 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