CVE-2007-6511
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 Enterprise 6.3.1 allows remote attackers to bypass content filtering by visiting http URLs with a (1) RealPlayer G2, (2) MSMSGS, or (3) StoneHttpAgent User-Agent header, which results in a Non-HTTP categorization.
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 confidenceWebsense Enterprise 6.3.1 incorrectly categorizes HTTP traffic as 'Non-HTTP' when the request includes specific User-Agent headers (RealPlayer G2, MSMSGS, or StoneHttpAgent), causing content filtering to be bypassed for those requests.
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.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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 Enterprise versionCheck the installed Websense Enterprise version by examining the product version in the Websense manager console, or run the command 'wseadmin --version' or check the registry/INI files in the Websense installation directory for version 6.3.1Affected if The installed version is exactly 6.3.1
-
Identify traffic with RealPlayer G2 User-AgentReview network logs, proxy logs, or Websense filtering logs for HTTP requests where the User-Agent header contains 'RealPlayer G2'Affected if HTTP traffic with User-Agent: RealPlayer G2 is present in logs and is categorized as 'Non-HTTP' instead of being filtered as HTTP content
-
Identify traffic with MSMSGS User-AgentReview network logs, proxy logs, or Websense filtering logs for HTTP requests where the User-Agent header contains 'MSMSGS'Affected if HTTP traffic with User-Agent: MSMSGS is present in logs and is categorized as 'Non-HTTP' instead of being filtered as HTTP content
-
Identify traffic with StoneHttpAgent User-AgentReview network logs, proxy logs, or Websense filtering logs for HTTP requests where the User-Agent header contains 'StoneHttpAgent'Affected if HTTP traffic with User-Agent: StoneHttpAgent is present in logs and is categorized as 'Non-HTTP' instead of being filtered as HTTP content
Your environment is affected if Websense Enterprise version 6.3.1 is installed AND HTTP traffic with RealPlayer G2, MSMSGS, or StoneHttpAgent User-Agent headers is being incorrectly classified as Non-HTTP, allowing content filtering to be bypassed.
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 Enterprise to a patched version that properly handles these User-Agent strings, or deploy supplementary network-level filtering to inspect and filter traffic regardless of User-Agent classification.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-6511 — 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-2007-6511 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