CVE-2015-2099
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 buffer overflows in WebGate Control Center allow remote attackers to execute arbitrary code via unspecified vectors to the (1) GetRecFileInfo function in the FileConverter.FileConverterCtrl.1 control, (2) Login function in the LoginContoller.LoginControllerCtrl.1 control, or (3) GetThumbnail function in the WESPPlayback.WESPPlaybackCtrl.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 · moderate confidenceMultiple buffer overflow vulnerabilities exist in WebGate Control Center's ActiveX controls (FileConverter.FileConverterCtrl.1, LoginContoller.LoginControllerCtrl.1, and WESPPlayback.WESPPlaybackCtrl.1). The GetRecFileInfo, Login, and GetThumbnail functions are vulnerable to unspecified vectors that can lead to remote 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 dataall 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.
-
Locate WebGate Control Center installationSearch for WebGate Control Center in program directories: Check C:\Program Files\WebGate or C:\Program Files (x86)\WebGate for any installed componentsAffected if WebGate Control Center or its components are found in the system
-
Identify vulnerable ActiveX controls via registryOpen Windows Registry Editor and navigate to HKEY_CLASSES_ROOT\ and search for the CLSIDs: FileConverter.FileConverterCtrl.1, LoginContoller.LoginControllerCtrl.1, WESPPlayback.WESPPlaybackCtrl.1Affected if Any of these three ActiveX control entries exist in the registry, indicating the vulnerable components are registered on the system
-
Enumerate registered ActiveX controls via command lineRun command 'reg query HKCR /s /f "FileConverter"' and similarly for "LoginContoller" and "WESPPlayback" to find registered CLSIDsAffected if The command returns CLSID entries for any of the three vulnerable controls
-
Check for the specific DLL implementationsSearch for WebGate DLL files in the installation directory, typically look for files like FileConverter.dll, LoginController.dll, or WESPPlayback.dllAffected if Any of these DLL files are found on the system, indicating the vulnerable ActiveX implementation is present
If WebGate Control Center is installed and any of the three ActiveX controls (FileConverter.FileConverterCtrl.1, LoginContoller.LoginControllerCtrl.1, or WESPPlayback.WESPPlaybackCtrl.1) are registered, the system is affected since all versions of these components are vulnerable.
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 dataLocate and update WebGate Control Center to a patched version, or disable the vulnerable ActiveX controls if no patch is available. Implement network segmentation to limit exposure to remote attackers.
- Consultation6.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,760.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2099 — 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-2099 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