CVE-2015-7918
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 the F1BookView ActiveX control in F1 Bookview in Schneider Electric ProClima before 6.2 allow remote attackers to execute arbitrary code via the (1) Attach, (2) DefinedName, (3) DefinedNameLocal, (4) ODBCPrepareEx, (5) ObjCreatePolygon, (6) SetTabbedTextEx, or (7) SetValidationRule method, a different vulnerability than CVE-2015-8561.
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 confidenceMultiple buffer overflow vulnerabilities exist in the F1BookView ActiveX control used by Schneider Electric ProClima (versions before 6.2). The vulnerabilities affect seven distinct methods (Attach, DefinedName, DefinedNameLocal, ODBCPrepareEx, ObjCreatePolygon, SetTabbedTextEx, and SetValidationRule), allowing remote attackers to achieve arbitrary code execution via specially crafted method calls.
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<= 6.1CVSS 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.
-
Verify ProClima installationCheck for ProClima installation by looking in Add/Remove Programs (Windows) or searching for ProClima in installed applicationsAffected if ProClima is installed and version is 6.1 or lower
-
Determine installed ProClima versionLocate ProClima in the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or check the executable properties of the ProClima program fileAffected if Installed version is 6.1 or earlier (versions before 6.2 are affected)
-
Identify F1BookView ActiveX control presenceSearch for the F1BookView control (CLSID: 8BD21B10-8B42-11D1-9C8F-00A0C93F8C93 or similar) in the Windows registry under HKLM\SOFTWARE\Classes\CLSIDAffected if The F1BookView ActiveX control is registered on the system
-
Check ActiveX control usage in Internet ExplorerIn Internet Explorer, go to Tools > Manage Add-ons and look for F1BookView or ProClima-related ActiveX controls; also check the Windows kill bit for this controlAffected if The vulnerable F1BookView ActiveX control is enabled or not blocked in Internet Explorer
A user is affected if Schneider Electric ProClima version 6.1 or earlier is installed with the F1BookView ActiveX control present and enabled in Internet Explorer, allowing the seven vulnerable methods to be exploited.
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 dataUpdate ProClima to version 6.2 or later to obtain the vendor patch. As an interim measure, disable the F1BookView ActiveX control in Internet Explorer or implement network-level isolation to restrict exposure to untrusted sources.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7918 — 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-7918 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