dbcve.org
Overall Equipment EffectivenessApplication · Sick

CVE-2022-27578

HIGH · 7.8 CVSS v3.1 Published 2022-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
An attacker can perform a privilege escalation through the SICK OEE if the application is installed in a directory where non authenticated or low privilege users can modify its content.

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

This is a privilege escalation vulnerability caused by insecure directory permissions on the SICK OEE application installation folder. When the application is installed in a directory writable by low-privilege or unauthenticated users, an attacker can modify executable files, DLLs, or configuration files within that directory. When a higher-privilege user subsequently runs the application, the modified code executes with elevated privileges, enabling privilege escalation.

MitigationReinstall SICK OEE in a directory with proper access controls, ensuring only administrative users have write permissions to the application files. Restrict file permissions to prevent modification by non-privileged users.

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
Overall Equipment EffectivenessApplication
Affected:= 0.5.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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. Identify if SICK OEE is installed
    Search for the SICK Overall Equipment Effectiveness application in the system registry (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall) or common installation directories such as C:\Program Files\SICK or C:\Program Files (x86)\SICK
    Affected if The application is found and installed on the system
  2. Determine the installed version
    Check the version information of the SICK OEE executable or check the registry entry under the uninstall key for the version value
    Affected if The installed version is exactly 0.5.1 (as the affected version is = 0.5.1)
  3. Locate the installation directory
    Find the installation path from the registry or by locating the main SICK OEE executable file
    Affected if The application installation directory has been identified and can be inspected
  4. Check directory permissions for weak access controls
    Right-click the installation folder, go to Properties > Security, and examine the permissions. Check which users and groups have Write or Modify permissions. Use the command 'icacls "<installation_path>"' to list all access control entries
    Affected if Users without administrative privileges, or possibly unauthenticated users, are granted Write or Modify permissions to the installation directory
  5. Inspect for modified or unexpected files
    Review the contents of the installation directory for any executable files (.exe), dynamic link libraries (.dll), or configuration files (.xml, .config, .ini) that appear altered, new, or unexpected
    Affected if Executable files, DLLs, or configuration files in the installation directory have been modified by an unauthorized user or contain unexpected changes

A user is affected if SICK OEE version 0.5.1 is installed in a directory where non-administrative users have write permissions, allowing potential modification of application binaries for privilege escalation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Reinstall SICK OEE in a directory with proper access controls, ensuring only administrative users have write permissions to the application files. Restrict file permissions to prevent modification by non-privileged users.

Recommended fix Moderate confidence
  1. Identify the current installation directory of the SICK OEE application
  2. Verify that the installation directory has permissions allowing write access from non-authenticated or low-privilege users (this is the vulnerability condition)
  3. Reinstall or move the SICK OEE application to a secure directory that is only writable by privileged users (e.g., C:\Program Files\SICK\ or /opt/sick/ on Linux)
  4. Configure filesystem permissions on the new installation directory so that only administrators or the service account have write access
  5. Ensure the application runs with the minimum privileges necessary for its function
  6. Restart the SICK OEE application service

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

Fix this in Overall Equipment Effectiveness Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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