dbcve.org
ProclimaApplication · Schneider Electric

CVE-2019-6824

CRITICAL · 9.8 CVSS v3.1 Published 2019-07-15
Fix available
A fix is available. Upgrade to 8.0.0 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
A CWE-119: Buffer Errors vulnerability exists in ProClima (all versions prior to version 8.0.0) which allows an unauthenticated, remote attacker to execute arbitrary code on the targeted system in all versions of ProClima prior to version 8.0.0.

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 confidence

This is a CWE-119 buffer errors vulnerability in Schneider Electric's ProClima software (versions prior to 8.0.0). The flaw allows an unauthenticated remote attacker to execute arbitrary code on the target system, likely due to improper bounds checking when processing input, leading to memory corruption.

MitigationUpgrade ProClima to version 8.0.0 or later to remediate this vulnerability.

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:< 8.0.0

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

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

  1. Confirm ProClima is installed
    Search for ProClima in the system application list (Windows: Control Panel > Programs and Features, or check for the installation directory typically under C:\Program Files\Schneider Electric\ProClima or similar)
    Affected if ProClima software is present on the system
  2. Identify installed ProClima version
    Right-click the ProClima executable (often named ProClima.exe), select Properties, and check the Details tab for the Product Version. Alternatively, check the uninstall entry in the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for a ProClima entry
    Affected if A version number is returned from the installation
  3. Compare version against affected range
    If a version is found, compare the first numeric component to 8.0.0. Versions are typically formatted as major.minor.patch (e.g., 7.2.1)
    Affected if The installed version is lower than 8.0.0 (e.g., 7.x.x, 6.x.x, or any version starting with 0-7)
  4. Verify ProClima service/executable is running
    Open Task Manager or use command 'tasklist | findstr -i ProClima' to check if the ProClima process is active
    Affected if The ProClima executable is currently running and the version is below 8.0.0

If ProClima is installed and the running version is any release prior to 8.0.0, the system is vulnerable to remote code execution via buffer overflow.

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 8.0.0 or later
Fixed in 8.0.0
Interim mitigation

Upgrade ProClima to version 8.0.0 or later to remediate this vulnerability.

Recommended fix High confidence

ProClima 8.0.0

  1. 1. Identify the current version of ProClima installed on the system
  2. 2. Download ProClima version 8.0.0 or later from the official Schneider Electric website (www.schneider-electric.com)
  3. 3. Back up any existing ProClima data, configurations, or project files according to Schneider Electric documentation
  4. 4. Uninstall the current version of ProClima
  5. 5. Install ProClima version 8.0.0 or later
  6. 6. Restore any backed-up data or configurations
  7. 7. Verify the installation by checking that ProClima runs without errors and confirming the version number
Caveat Review Schneider Electric release notes for version 8.0.0 to assess any functional changes or migration requirements from previous versions

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

Fix this in Proclima Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-6824 — 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-2019-6824 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