CVE-2006-6622
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 · uneditedSoft4Ever Look 'n' Stop (LnS) 2.05p2 before 20061215 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 · high confidenceSoft4Ever Look 'n' Stop firewall versions before 20061215 use Process Environment Block (PEB) fields (ImagePathName, CommandLine, WindowTitle) to identify processes for filtering rules. Local attackers can manipulate these PEB fields to spoof legitimate processes and bypass firewall 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 productCheck Programs and Features or use 'wmic product get name' to list installed security softwareAffected if Any of these products are installed: AVG Antivirus Plus Firewall, Comodo Personal Firewall, Filseclab Personal Firewall, Infoprocess Antihook, Soft4Ever Look 'n' Stop, or Symantec Sygate Personal Firewall
-
Check installed firewall versionOpen the firewall application UI and navigate to About/Help or use 'wmic product get version' to find the exact version numberAffected if Version matches one of these affected builds: AVG 7.5.431, Comodo 2.3.6.81, Filseclab 3.0.8686, Infoprocess 3.0.23, Soft4Ever Look 'n' Stop 2.05p2, or Sygate 5.6.2808
-
Confirm Look 'n' Stop version for patched statusFor Soft4Ever Look 'n' Stop specifically, check if version is earlier than 20061215 by examining the build number in the application About sectionAffected if Look 'n' Stop version is before build 20061215 (the 2.05p2 build listed is affected)
-
Verify local user accessReview system audit logs and user account permissions to determine if untrusted local users have interactive or remote access to the systemAffected if Untrusted or low-privilege local users have access to log into the system interactively, as this enables PEB manipulation
A user is affected if they have any of the listed firewall products installed at the exact versions specified (or Look 'n' Stop versions before 20061215) AND untrusted local users can access the system.
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 Look 'n' Stop version 20061215 or later which implements more secure process identification beyond PEB fields.
- Consultation2.0 h
- Implementation12.0 h
- Testing6.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 $6,688.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-6622 — 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-6622 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