dbcve.org
Scadapro ClientApplication · Measuresoft

CVE-2022-2898

MEDIUM · 5.5 CVSS v3.1 Published 2022-08-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
Measuresoft ScadaPro Server and Client (All Versions) do not properly resolve links before file access; this could allow a denial-of-service condition.

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

Measuresoft ScadaPro Server and Client (all versions) fail to properly resolve symbolic links or relative path references before performing file access operations. This improper link resolution could cause the application to access unintended files or trigger resource exhaustion, leading to a denial-of-service condition.

MitigationSince all versions are affected with no specified patch, implement network segmentation to isolate ScadaPro systems, apply strict file system permissions to limit accessible paths, and monitor for anomalous file access patterns that may indicate exploitation.

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
Scadapro ClientApplication
Affected:all versions
Scadapro ServerApplication
Affected:all versions

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 ScadaPro installation presence
    Search for ScadaPro executables, services, or installation directories on the system. Check for processes named 'ScadaPro', 'scadapro', or related service entries using task manager or command-line tools like 'tasklist' or 'Get-Process'. Also look in common installation paths such as Program Files or Program Files (x86).
    Affected if ScadaPro Server or Client software is found installed on the system - all versions are affected by this vulnerability.
  2. Identify ScadaPro running services
    Check for running ScadaPro services or processes using 'sc query' command or review running services in the system service manager. Note any active ScadaPro-related services or daemon processes.
    Affected if ScadaPro services are currently running - the vulnerable file access code is active and could be exploited.
  3. Review ScadaPro configuration files
    Locate and examine ScadaPro configuration files in the installation directory for settings related to file access, path resolution, or symbolic link handling. Look for configuration parameters that control file operations or path validation.
    Affected if Configuration files exist and contain settings related to file access or path handling - the vulnerable code path may be reachable through these settings.
  4. Check file system permissions on ScadaPro directories
    Review file system ACLs on ScadaPro installation directories and any directories the application is configured to access. Use 'icacls' or similar tools to list permissions and identify if low-privilege accounts have access.
    Affected if ScadaPro directories have overly permissive ACLs - an attacker could exploit the symlink vulnerability to access unintended files.
  5. Audit network exposure of ScadaPro services
    Use 'netstat -an' or similar network tools to identify ports and bindings for ScadaPro services. Determine if ScadaPro Server or Client ports are exposed to untrusted networks.
    Affected if ScadaPro services are listening on network interfaces accessible from untrusted networks - remote exploitation becomes possible.

If Measuresoft ScadaPro Server or Client software is installed on the system (regardless of version), the environment is affected because all versions contain the improper symbolic link resolution vulnerability in file access operations.

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

Since all versions are affected with no specified patch, implement network segmentation to isolate ScadaPro systems, apply strict file system permissions to limit accessible paths, and monitor for anomalous file access patterns that may indicate exploitation.

Fix this in Scadapro Client Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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