CVE-2006-6620
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 · uneditedComodo Personal Firewall 2.3.6.81 relies on the Process Environment Block (PEB) to identify a process, which allows local users to bypass the product's controls on a process by spoofing the (1) ImagePathName, (2) CommandLine, and (3) WindowTitle fields in the PEB.
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 confidenceComodo Personal Firewall 2.3.6.81 uses the Process Environment Block (PEB) to identify processes for its security controls. Local attackers can manipulate the ImagePathName, CommandLine, and WindowTitle fields in the PEB to spoof a malicious process as a trusted application, thereby bypassing the firewall's access 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.5.431= 2.3.6.81= 3.0.8686= 3.0.23= 2.05p2= 5.6.2808CVSS 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.
-
Identify installed firewall productOpen Control Panel > Programs and Features, or run 'wmic product get name,version' to list installed software. Look for: Comodo Personal Firewall, AVG Antivirus Plus Firewall, Filseclab Personal Firewall, Infoprocess Antihook, Look N Stop, or Symantec Sygate Personal Firewall.Affected if Any of these firewall products is installed.
-
Check firewall version numberRight-click the firewall application in the system tray or Programs and Features, select About or Properties, or check the version in the program's Help > About section. Compare against these vulnerable versions: Comodo Personal Firewall 2.3.6.81, AVG Antivirus Plus Firewall 7.5.431, Filseclab Personal Firewall 3.0.8686, Infoprocess Antihook 3.0.23, Look N Stop 2.05p2, or Symantec Sygate Personal Firewall 5.6.2808.Affected if The installed version exactly matches one of these vulnerable versions.
-
Verify firewall uses process-based rulesOpen the firewall configuration interface and examine the rule set. Look for rules that allow or block applications based on process name, executable path, or process window title rather than network signature or port-based rules.Affected if The firewall has application-based rules that rely on process identification (process name, path, or window title).
-
Check for process identification methodReview firewall documentation or examine its behavior. The firewall identifies processes by reading PEB fields (ImagePathName, CommandLine, WindowTitle). If the firewall does not perform additional verification such as digital signature checking, code integrity validation, or cryptographic process tokens, it relies solely on PEB data.Affected if The firewall relies solely on PEB data without additional process verification like signature validation.
You are affected if any of these specific firewall products is installed at exactly the listed vulnerable version AND the firewall uses application-based rules that rely on PEB process identification without additional verification.
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 newer version of Comodo Personal Firewall that implements more robust process identification methods not reliant solely on PEB data, or implement additional verification mechanisms such as digital signature verification or cryptographic process tokens.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-6620 — 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-2006-6620 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