Scadapro ServerApplication · Measuresoft

CVE-2022-2896

HIGH · 7.8 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 →
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
Measuresoft ScadaPro Server (All Versions) allows use after free while processing a specific 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

Measuresoft ScadaPro Server contains a use-after-free vulnerability when parsing project files. The vulnerability allows memory to be accessed after it has been freed during project file processing, potentially enabling arbitrary code execution or denial of service.

MitigationRestrict access to ScadaPro Server and validate all project files before opening. Contact Measuresoft for vendor patches as all versions are affected.

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 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
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. Confirm ScadaPro Server installation
    Check for ScadaPro Server in installed programs (Windows: Programs and Features, Linux: package manager) or look for ScadaPro executables in common installation directories
    Affected if ScadaPro Server is found installed on the system
  2. Identify ScadaPro Server process
    Check running processes for ScadaPro Server or related service (look for process names containing 'scadapro' or 'measuresoft')
    Affected if A ScadaPro Server process is running or available to run
  3. Verify project file handling capability
    Check if the ScadaPro Server installation includes project file parsing modules (.scadapro, .spj, or similar project file extensions) and if the server is configured to accept or load project files
    Affected if Project file parsing modules exist and the server can load project files
  4. Check network exposure
    Review network configuration to determine if ScadaPro Server listens on network ports or accepts remote project file imports
    Affected if The server accepts project files from network sources or external input

If ScadaPro Server is installed and can process project files, the environment is affected since all versions contain the use-after-free vulnerability in project file parsing.

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

Restrict access to ScadaPro Server and validate all project files before opening. Contact Measuresoft for vendor patches as all versions are affected.

Fix this in Scadapro Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-2896 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