CVE-2011-1827
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 · uneditedMultiple unspecified vulnerabilities in Check Point SSL Network Extender (SNX), SecureWorkSpace, and Endpoint Security On-Demand, as distributed by SecurePlatform, IPSO6, Connectra, and VSX, allow remote attackers to execute arbitrary code via vectors involving a (1) ActiveX control or (2) Java applet.
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 confidenceMultiple unspecified vulnerabilities in Check Point SSL Network Extender (SNX), SecureWorkSpace, and Endpoint Security On-Demand allow remote attackers to execute arbitrary code via malicious ActiveX controls or Java applets. The affected products were distributed through SecurePlatform, IPSO6, Connectra, and VSX platforms.
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= r66.1= r66.1n= r65.70= r70.40= r71.30= r75= r65.20= r67CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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 Check Point productRun 'ps' or check system inventory to list installed Check Point software packages. Look for Connectra, VPN-1, Endpoint Security, or SSL Network Extender (SNX) components.Affected if Any of these Check Point products are installed on the system
-
Check product versionUse the product-specific version command or check /etc/cp* release files to determine the exact version number of the installed Check Point software.Affected if Version matches r65.70, r70.40, r71.30, r75, r66.1, r66.1n, r65.20, or r67
-
Identify platform typeCheck the underlying operating system platform. Determine if the system runs SecurePlatform (SPLAT), IPSO6, or VSX.Affected if System runs on SecurePlatform, IPSO6, Connectra, or VSX platforms with the affected versions above
-
Check for SNX or client componentsLook for SSL Network Extender (SNX), SecureWorkSpace, or Endpoint Security client installations. Check browser add-ons or installed extensions.Affected if SNX, SecureWorkSpace, or Endpoint Security client components are present and active
-
Verify browser plugin exposureInspect browser configuration to determine if ActiveX controls and Java plugins are enabled for the Check Point management interfaces.Affected if ActiveX or Java plugins are enabled and accessible to untrusted content sources
The system is affected if it runs any of the listed Check Point product versions (r65.70, r70.40, r71.30, r75, r66.1, r66.1n, r65.20, r67) on SecurePlatform, IPSO6, Connectra, or VSX platforms with SNX or client components that allow ActiveX/Java execution.
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 dataDisable ActiveX and Java browser plugins on affected systems where possible, apply available Check Point patches for these products, and implement network-level controls to restrict communication with untrusted ActiveX/Java content sources.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1827 — 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-2011-1827 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