dbcve.org
Zelio Soft 2Application · Schneider Electric

CVE-2019-6822

HIGH · 7.8 CVSS v3.1 Published 2019-07-15
Fix available
A fix is available. Upgrade to after 5.2 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 Use After Free: CWE-416 vulnerability exists in Zelio Soft 2, V5.2 and earlier, which could cause remote code execution when opening a specially crafted Zelio Soft 2 project file.

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

A Use After Free (CWE-416) vulnerability in Zelio Soft 2 versions 5.2 and earlier allows remote code execution when a user opens a specially crafted project file. The vulnerability stems from improper memory management during file parsing, where memory is freed but still accessed, leading to arbitrary code execution.

MitigationUpdate Zelio Soft 2 to a version newer than V5.2 if a vendor patch is available; otherwise, avoid opening untrusted project files and deploy compensating controls such as endpoint protection and network segmentation.

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
Zelio Soft 2Application
Affected:<= 5.2

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
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 checks

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

  1. Check if Zelio Soft 2 is installed
    Look for Zelio Soft 2 in the Windows Add/Remove Programs list, or search for the executable file (typically named ZelioSoft2.exe) in Program Files folders
    Affected if Zelio Soft 2 is present on the system
  2. Determine the installed version
    Right-click the ZelioSoft2.exe file, select Properties, and check the Version tab. Alternatively, open the application and look for the version information in the Help menu or About dialog
    Affected if The reported version number is 5.2 or lower (such as 5.2, 5.1, 5.0, or earlier)
  3. Confirm the exact version number against affected range
    Compare your identified version to the affected range: all versions <= 5.2 are vulnerable. If the version shows only '5.2' without a sub-version number, treat it as affected
    Affected if The version is 5.2 or any earlier version number, including beta or preview releases

You are affected if Zelio Soft 2 is installed and the version is 5.2 or any earlier version.

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.

From vendor data
Upgrade available Upgrade to a release after 5.2
Interim mitigation

Update Zelio Soft 2 to a version newer than V5.2 if a vendor patch is available; otherwise, avoid opening untrusted project files and deploy compensating controls such as endpoint protection and network segmentation.

Fix this in Zelio Soft 2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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