dbcve.org
ProclimaApplication · Schneider Electric

CVE-2014-8511

HIGH · 10.0 CVSS v2.0 Published 2014-12-27
Fix available
A fix is available. Upgrade to after 6.0.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Buffer overflow in an ActiveX control in Atx45.ocx in Schneider Electric ProClima before 6.1.7 allows remote attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2014-8512. NOTE: this may be clarified later based on details provided by researchers.

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 confidence

Buffer overflow vulnerability in the Atx45.ocx ActiveX control in Schneider Electric ProClima before version 6.1.7 allows remote attackers to execute arbitrary code via unspecified vectors.

MitigationUpdate ProClima to version 6.1.7 or later to replace the vulnerable ActiveX control. Consider disabling ActiveX controls in Internet Explorer as a defense-in-depth measure if updates cannot be applied immediately.

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
ProclimaApplication
Affected:<= 6.0.1

CVSS 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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify ProClima installation
    Check for ProClima installation in the Windows registry under HKLM\SOFTWARE\Schneider Electric\ProClima or HKLM\SOFTWARE\Wow6432Node\Schneider Electric\ProClima, or look for the ProClima application folder in Program Files.
    Affected if ProClima is installed and the version is 6.0.1 or lower, or if the version cannot be determined but ProClima appears to be installed.
  2. Determine ProClima version
    Open the Windows registry key HKLM\SOFTWARE\Schneider Electric\ProClima\CurrentVersion (or the Wow6432Node equivalent) and read the Version value, or right-click the ProClima executable in Program Files and view Properties.
    Affected if The installed version is 6.0.1 or lower, or no version can be verified.
  3. Locate Atx45.ocx ActiveX control
    Search for Atx45.ocx in the ProClima installation directory (commonly C:\Program Files\Schneider Electric\ProClima or similar), and check the Windows\System32 folder.
    Affected if The Atx45.ocx file exists on the system.
  4. Check Atx45.ocx file version
    Right-click the Atx45.ocx file, select Properties, and view the Version tab to see the file version and product version.
    Affected if The file exists and its version is unknown or matches versions shipped with ProClima 6.0.1 or earlier.

The system is affected if Schneider Electric ProClima is installed with version 6.0.1 or lower, or if the Atx45.ocx ActiveX control from those versions is present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 6.0.1
Interim mitigation

Update ProClima to version 6.1.7 or later to replace the vulnerable ActiveX control. Consider disabling ActiveX controls in Internet Explorer as a defense-in-depth measure if updates cannot be applied immediately.

Recommended fix High confidence

ProClima 6.1.7 or later

  1. Download ProClima version 6.1.7 or later from the official Schneider Electric download portal (download.schneider-electric.com)
  2. Verify the downloaded file integrity using checksums if provided by Schneider Electric
  3. Close any running instances of ProClima
  4. Install the updated ProClima version following standard installation procedures
  5. Restart the system if required by the installer
  6. Verify the installed version matches 6.1.7 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Proclima Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-8511 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-8511 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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