CVE-2010-5147
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 Remote Filtering component in Websense Web Security and Web Filter before 6.3.3 Hotfix 18 and 7.x before 7.1.1 allows remote attackers to cause a denial of service (daemon exit) via a large volume of traffic.
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 confidenceA denial of service vulnerability exists in the Remote Filtering component of Websense Web Security and Web Filter. Attackers can cause the filtering daemon to exit/crash by sending a large volume of traffic to the Remote Filtering service.
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.3.3= 6.3.0= 6.3.1= 6.3.2= 7.0= 7.1<= 6.3.3= 6.3.0= 6.3.1= 6.3.2= 7.0= 7.1CVSS 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
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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 Websense installation and product typeLocate the Websense installation directory or check installed programs on the Windows server. Look for 'Websense Web Security' or 'Websense Web Filter' product names.Affected if Either product is installed, proceed to version check.
-
Determine installed Websense versionOpen the Websense manager or check the program files for version information. Common locations: C:\Program Files\Websense\ or check the 'About' dialog in Websense Administrator.Affected if Version is <= 6.3.3, 6.3.0, 6.3.1, 6.3.2, 7.0, or 7.1 - these are all within the affected range.
-
Confirm Remote Filtering service is enabledCheck the Websense configuration for Remote Filtering settings. This is typically found in the Websense Administrator console under Remote Filtering or Filtering Service configuration.Affected if Remote Filtering component is enabled and configured, the vulnerability is present.
-
Check for recent filtering daemon crashesReview Websense log files (typically in the Websense logs directory) for entries indicating the filtering daemon (wsfcs.exe or similar) has exited or crashed unexpectedly.Affected if Daemon crashes are logged and the version is within affected range, the CVE may have been exploited.
-
Verify Remote Filtering service network exposureExamine network configuration to determine if the Remote Filtering port (typically port 15872 or similar) is exposed to untrusted networks or the internet.Affected if Remote Filtering service is accessible from outside the trusted network, the attack surface is present.
You are affected if Websense Web Security or Web Filter version 6.3.0-6.3.3, 7.0, or 7.1 is installed with the Remote Filtering component enabled and exposed.
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 Websense Web Security and Web Filter to version 6.3.3 Hotfix 18 or later, or version 7.1.1 or later. If immediate patching is not possible, consider implementing network-level controls to rate-limit or restrict traffic to the Remote Filtering component.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-5147 — 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-2010-5147 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