CVE-2015-2100
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 stack-based buffer overflows in WebGate eDVR Manager and Control Center allow remote attackers to execute arbitrary code via unspecified vectors to the (1) TCPDiscover or (2) TCPDiscover2 function in the WESPDiscovery.WESPDiscoveryCtrl.1 control.
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 confidenceStack-based buffer overflow in WebGate eDVR Manager and Control Center's WESPDiscovery ActiveX control (WESPDiscovery.WESPDiscoveryCtrl.1). The TCPDiscover and TCPDiscover2 functions fail to properly validate input bounds, allowing remote attackers to overwrite stack memory and execute arbitrary code via specially crafted network packets.
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 dataall 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
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 WebGate software installationCheck installed programs for 'WebGate Control Center' or 'WebGate Edvr Manager' in Windows Add/Remove Programs or via registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\UninstallAffected if Either product is listed as installed, the system may be running vulnerable software
-
Locate the WESPDiscovery ActiveX controlCheck for the ActiveX control registration in the Windows registry under HKLM\SOFTWARE\Classes\WESPDiscovery.WESPDiscoveryCtrl.1 or HKCR\CLSID\ searching for the CLSID associated with this controlAffected if The WESPDiscovery ActiveX control is registered on the system
-
Identify discovery service network listenersUse netstat or PowerShell to check for listening TCP ports commonly used by WebGate discovery services (typically ports in the 8000-9000 range or as configured); run: netstat -an | findstr LISTENINGAffected if A TCP listener is bound to a WebGate discovery service port
-
Confirm browser or client usage of the ActiveX controlCheck Internet Explorer security settings or enterprise policy configurations for ActiveX control permissions related to WESPDiscovery; inspect browser add-ons or BHOsAffected if The ActiveX control is permitted to run in browsers or is loaded by the eDVR Manager client application
If WebGate Control Center or eDVR Manager is installed with the WESPDiscovery ActiveX control present and the discovery service is exposed, the system is vulnerable to remote code execution via crafted network packets.
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 dataApply available vendor patches if released; otherwise, network isolate affected systems, block external access to discovery services on TCP ports, and restrict the ActiveX control execution through browser/endpoint security policies.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2100 — 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-2100 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