CVE-2015-5624
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 · uneditedBuffer overflow in the ExecCall method in c2lv6.ocx in the FreeBit ELPhoneBtnV6 ActiveX control allows remote attackers to execute arbitrary code via a crafted HTML document, related to the discontinued "Click to Live" service.
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 confidenceBuffer overflow in the ExecCall method in c2lv6.ocx (FreeBit ELPhoneBtnV6 ActiveX control) allows remote attackers to execute arbitrary code via a crafted HTML document. The vulnerability is associated with the discontinued 'Click to Live' service.
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
- 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 the c2lv6.ocx ActiveX control fileSearch the system for the file c2lv6.ocx using Windows Explorer search or the command: dir /s /b c:\*c2lv6.ocxAffected if The file c2lv6.ocx exists on the system
-
Check if the control is registered in Windows RegistryLook for the control's CLSID in the registry under HKEY_CLASSES_ROOT\CLSID. The ProgID for this control is typically 'ELPHONEBTNV6.ElePhoneBtnV6Ctrl.1' or similar. Use regedit or reg query to search for 'ELPhoneBtnV6'Affected if The ActiveX control is registered in the Windows registry and available for instantiation in browsers or other applications
-
Check if the control is marked as Safe for ScriptingCheck the registry under the CLSID for the control for the value 'SafeForScripting' set to 1, or check the Internet Explorer ActiveX compatibility settingsAffected if The control is marked as Safe for Scripting in the registry, enabling it to run in web pages without user prompts
-
Verify if the control loads in Internet ExplorerOpen Internet Explorer and check if the control can be instantiated. In IE, navigate to Tools > Manage Add-ons and look for 'ELPhoneBtnV6' or 'Click to Live' related add-onsAffected if The FreeBit ELPhoneBtnV6 ActiveX control appears in the list of installed/loaded add-ons in Internet Explorer
The system is affected if the c2lv6.ocx ActiveX control file exists and is registered, particularly if marked as Safe for Scripting, since the vulnerability allows arbitrary code execution through the ExecCall method without requiring specific version matching (all versions are affected).
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 FreeBit ELPhoneBtnV6 ActiveX control (c2lv6.ocx) from affected systems. Configure browser security settings to prevent ActiveX controls from running or prompt before running, especially for untrusted sites.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5624 — 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-5624 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