CVE-2019-6825
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 · uneditedA CWE-427: Uncontrolled Search Path Element vulnerability exists in ProClima (all versions prior to version 8.0.0) which could allow a malicious DLL file, with the same name of any resident DLLs inside the software installation, to execute arbitrary code 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 confidenceA CWE-427 Uncontrolled Search Path Element vulnerability in ProClima allows DLL hijacking. The software loads DLLs from insecure search paths, enabling attackers to place malicious DLLs with names matching legitimate resident DLLs to achieve arbitrary 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 data< 8.0.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Identify ProClima installation and versionCheck Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for ProClima, or locate the ProClima executable (typically ProClima.exe) and check its file properties for version informationAffected if Installed version is below 8.0.0 or version cannot be determined
-
Locate ProCloma installation directoryFind the directory where ProClima is installed (commonly C:\Program Files\Schneider Electric\ProClima or similar). Use registry key 'InstallLocation' or right-click the executable to view its pathAffected if Installation directory is in a location with weak access controls or on a network share
-
Verify DLL search path vulnerabilityRun Process Monitor or similar tool while launching ProClima, filter by the process name and look for DLL load events. Check if the software attempts to load DLLs from the current working directory, application directory, or other insecure pathsAffected if ProClima loads DLLs from directories other than its own installation folder or system directories
-
Check installation directory permissionsRight-click the ProClima installation folder, go to Properties > Security, and verify which users have Write or Modify permissions. Also check if the folder inherits permissions from a parent with broad accessAffected if Non-admin users or potentially untrusted accounts have Write access to the ProClima installation directory
The environment is affected if ProClima version is below 8.0.0 AND the installation directory or search path configuration allows untrusted DLLs to be loaded.
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 data8.0.0
Upgrade ProClima to version 8.0.0 or later, which contains the fix for the uncontrolled DLL search path vulnerability.
- 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-2019-6825 — 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-2019-6825 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