CVE-2010-5149
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 · uneditedWebsense Web Security and Web Filter before 6.3.3 Hotfix 27 and 7.x before 7.1.1 allow remote attackers to cause a denial of service (Blue Coat appliance integration outage) via a long URL.
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 confidenceThis is a denial of service vulnerability in Websense Web Security and Web Filter products. Remote attackers can cause the Blue Coat appliance integration to fail by sending a specially crafted long URL to the affected Websense installation.
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.
-
Identify Websense product installationCheck for Websense Web Security or Web Filter installation by examining the system for websense-related processes, services, or directories. Common paths include C:\Program Files\Websense or /opt/websense/.Affected if Websense Web Security or Web Filter software is found on the system
-
Determine installed versionLocate and read the version information file or use the Websense administrative interface. The version is typically stored in a file named version.ini, about.htm, or can be retrieved via the Websense Manager UI under Help > About.Affected if The installed version is 6.3.0, 6.3.1, 6.3.2, 6.3.3, 7.0, or 7.1
-
Verify Blue Coat integration is configuredExamine the Websense configuration for Blue Coat appliance integration settings. This is typically found in the Websense Manager under Integration > Blue Coat or in the icap.conf / proxy.conf configuration files.Affected if Blue Coat appliance integration is enabled or configured in the Websense settings
-
Check for DoS indicatorsReview Websense logs, system event logs, or crash dump files for errors related to long URL processing and Blue Coat integration failures. Look for entries containing 'Blue Coat', 'URL', 'overflow', 'crash', or denial-of-service related errors.Affected if Logs show failures, crashes, or errors specifically related to Blue Coat appliance integration when processing URLs
A system is affected if it runs Websense Web Security or Web Filter version 6.3.0 through 7.1 with Blue Coat appliance integration enabled and is experiencing integration failures.
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/Web Filter to version 6.3.3 Hotfix 27 or later, or 7.1.1 or later, to patch the vulnerability.
- 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-2010-5149 — 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-5149 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