CVE-2010-5190
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 Active Content Transformation functionality in Blue Coat ProxySG before SGOS 4.3.4.2, 5.x before SGOS 5.4.5.1, 5.5 before SGOS 5.5.4.1, and 6.x before SGOS 6.1.2.1 allows remote attackers to bypass JavaScript detection via HTML entities.
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 confidenceThe Active Content Transformation in Blue Coat ProxySG fails to properly decode HTML entities when analyzing JavaScript content, allowing attackers to evade JavaScript detection by encoding script tags and keywords using HTML entity notation (e.g., <script> instead of <script>).
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<= 4.3.4= 3.2.6= 4.1.2.1= 4.2.1.2= 4.2.1.6= 4.2.2= 4.2.2.1= 4.2.2.2= 4.2.3= 4.2.3.4= 4.2.3.7= 4.2.3.12all versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/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.
-
Identify the SGOS versionAccess the ProxySG management console or CLI and run 'show version' to retrieve the installed SGOS versionAffected if The version matches any of these: 3.2.6, 4.1.2.1, 4.2.1.2, 4.2.1.6, 4.2.2, 4.2.2.1, 4.2.2.2, 4.2.3, 4.2.3.4, 4.2.3.7, 4.2.3.12, or is 4.3.4 or earlier; or for general ProxySG without specific SGOS version listed, compare your version to the affected ranges
-
Confirm the ProxySG modelRun 'show hardware' or check the management console for the specific model number (SG210 or SG510 series)Affected if The device is a Proxysg SG210 or SG510 series running any version
-
Check if Active Content Transformation is enabledIn the ProxySG management console, navigate to Content Filtering > Active Content Transformation (or use CLI 'show content-filter act') to see if ACT processing is turned onAffected if Active Content Transformation is enabled and the SGOS version or model is in the affected list
-
Verify JavaScript analysis is activeConfirm that the ProxySG is configured to analyze JavaScript content - check Content Policy settings or threat profiling for JavaScript detectionAffected if JavaScript analysis or script filtering is active and the version/model is vulnerable
A system is affected if it runs a vulnerable SGOS version or is a Proxysg SG210/SG510 model, AND has Active Content Transformation enabled for JavaScript content analysis.
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 ProxySG to SGOS 4.3.4.2, 5.4.5.1, 5.5.4.1, 6.1.2.1 or later. As a workaround, disable Active Content Transformation or implement supplementary web filtering.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-5190 — 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-5190 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