CVE-2011-5086
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 · uneditedhttps50.ocx in IP*Works! SSL in the server in Unitronics UniOPC before 2.0.0 does not properly implement an unspecified function, which allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted web site.
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 confidenceThe vulnerability exists in the https50.ocx ActiveX control (IP*Works! SSL) bundled with Unitronics UniOPC servers prior to version 2.0.0. The control fails to properly implement an unspecified function, allowing remote attackers to trigger the vulnerability through a crafted website that loads the ActiveX control, resulting in application crash (denial of service) or potential arbitrary code execution.
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<= 1.3.8CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/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.
-
Locate Unitronics UniOPC installation directorySearch for UniOPC installation folders, typically under C:\Program Files\Unitronics or C:\Program Files (x86)\Unitronics, or check Add/Remove Programs for installed softwareAffected if UniOPC server software is found on the system
-
Check installed UniOPC versionRight-click the UniOPC application in Add/Remove Programs, view its properties, or check version info in the installation folder. Compare the version number to the affected range <= 1.3.8Affected if The installed version is 1.3.8 or any earlier version (1.x series)
-
Verify presence of vulnerable https50.ocx fileSearch the UniOPC installation directory for the file https50.ocx. This is the IP*Works! SSL ActiveX controlAffected if The file https50.ocx exists in the UniOPC installation folder
-
Check if ActiveX control is registeredOpen Windows Command Prompt and run: reg query "HKLM\SOFTWARE\Classes\TypeLib\{F1F5C6C1-E8B2-11D1-9A5C-0000F80710DB}" or search for the https50.ocx CLSID in the registryAffected if The ActiveX control is registered in the Windows registry
A system is affected if Unitronics UniOPC version 1.3.8 or earlier is installed and the vulnerable https50.ocx ActiveX control is present and registered.
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 Unitronics UniOPC to version 2.0.0 or later to obtain the patched https50.ocx control. Consider disabling the ActiveX control in browser security zones or implementing network segmentation to limit exposure to web-based attacks until the upgrade is applied.
- Consultation2.0 h
- Implementation4.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-5086 — 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-5086 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