dbcve.org
Flexi Soft DesignerApplication · Sick

CVE-2022-27579

HIGH · 7.8 CVSS v3.1 Published 2022-07-19
Fix available
A fix is available. Upgrade to 1.9.4 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 deserialization vulnerability in a .NET framework class used and not properly checked by Flexi Soft Designer in all versions up to and including 1.9.4 SP1 allows an attacker to craft malicious project files. Opening/importing such a malicious project file would execute arbitrary code with the privileges of the current user when opened or imported by the Flexi Soft Designer. This compromises confidentiality integrity and availability. For the attack to succeed a user must manually open a malicious 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 · high confidence

Flexi Soft Designer contains a deserialization vulnerability in a .NET framework class used for processing project files. The application does not properly validate or sanitize data during deserialization, allowing specially crafted malicious project files to deserialize and execute arbitrary code with the privileges of the user who opens the file.

MitigationUpgrade Flexi Soft Designer to a version beyond 1.9.4 SP1 that patches this vulnerability. Until patched, users should not open project files from untrusted sources.

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
Flexi Soft DesignerApplication
Affected:< 1.9.4= 1.9.4

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. Locate the Flexi Soft Designer installation
    Open Windows Control Panel > Programs and Features, or check the installation directory (typically C:\Program Files\SICK\Flexi Soft Designer\) for the executable file.
    Affected if The application is installed on this system.
  2. Determine the installed version number
    Right-click on the Flexi Soft Designer executable (e.g., FlexiSoftDesigner.exe) and select Properties > Details to view the File Version. Alternatively, in Programs and Features, locate the entry and note the version shown.
    Affected if The version displayed is lower than 1.9.4, or shows exactly 1.9.4.
  3. Verify the specific version against affected range
    Compare your identified version to the affected range: versions < 1.9.4 and version = 1.9.4 are vulnerable. Versions 1.9.4 SP1 or later are not affected.
    Affected if Your installed version is 1.9.4 or any earlier version (e.g., 1.9.3, 1.9.2, 1.8.x, etc.).
  4. Assess project file handling practices
    Identify where project files (.fsp or similar extensions used by Flexi Soft Designer) are stored and whether users routinely open files from external or untrusted sources.
    Affected if Users open project files received from external parties or unknown sources without verification.

Your environment is affected if Flexi Soft Designer version 1.9.4 or any earlier version is installed and users may open project files from untrusted sources.

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

Upgrade Flexi Soft Designer to a version beyond 1.9.4 SP1 that patches this vulnerability. Until patched, users should not open project files from untrusted sources.

Recommended fix Moderate confidence

Flexi Soft Designer version greater than 1.9.4 SP1 (contact SICK support for exact fixed release)

  1. 1. Navigate to the SICK software download page or contact SICK support to obtain the latest version of Flexi Soft Designer
  2. 2. Download the fixed version of Flexi Soft Designer (version higher than 1.9.4 SP1)
  3. 3. Uninstall the current vulnerable version of Flexi Soft Designer
  4. 4. Install the newly downloaded fixed version
  5. 5. Verify the installation by opening Flexi Soft Designer and confirming the version number
  6. 6. Do not open any untrusted or unknown project files in Flexi Soft Designer to avoid potential deserialization attacks
Caveat Review SICK release notes for any configuration or project file changes that may require adjustments

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

Fix this in Flexi Soft Designer Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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