CVE-2015-2096
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 · uneditedUse-after-free vulnerability in the Connect function in the WESPMonitor.WESPMonitorCtrl.1 ActiveX control in WebGate eDVR Manager allows remote attackers to execute arbitrary code via an invalid IP address and a page reload.
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 confidenceUse-after-free vulnerability in the Connect function of the WESPMonitor.WESPMonitorCtrl.1 ActiveX control in WebGate eDVR Manager allows remote attackers to execute arbitrary code by providing an invalid IP address and triggering a page reload.
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= 2.6.4CVSS 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.
-
Check if WebGate eDVR Manager is installedLook for the application in Programs and Features (Add/Remove Programs) or check for installation directories such as C:\Program Files\WebGate\eDVR Manager or C:\Program Files (x86)\WebGate\eDVR ManagerAffected if WebGate eDVR Manager version 2.6.4 is installed
-
Verify the installed version of WebGate eDVR ManagerRight-click on the application in Programs and Features, select Properties, and check the version field, or locate the main executable and view its file propertiesAffected if The version listed is 2.6.4 exactly
-
Check if the WESPMonitor ActiveX control is registeredOpen Windows Registry and navigate to HKEY_CLASSES_ROOT\WESPMonitor.WESPMonitorCtrl.1, or use regsvr32 to check registration status of the controlAffected if The WESPMonitor.WESPMonitorCtrl.1 CLSID {E1C8C350-6D8B-11D9-8867-0050BA0FC256} is present in the registry
-
Confirm the ActiveX DLL file exists on the systemSearch for WESPMonitor.dll in the WebGate eDVR Manager installation directory or in C:\Windows\System32Affected if WESPMonitor.dll exists and corresponds to the vulnerable version 2.6.4
A user is affected if WebGate eDVR Manager version 2.6.4 is installed AND the WESPMonitor.WESPMonitorCtrl.1 ActiveX control is registered on the system.
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 or remove the vulnerable WESPMonitor ActiveX control in WebGate eDVR Manager, and restrict ActiveX execution through browser security settings or group policy to prevent exploitation.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2096 — 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-2015-2096 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