CVE-2022-2897
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 · uneditedMeasuresoft ScadaPro Server and Client (All Versions) do not properly resolve links before file access; this could allow privilege escalation..
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 confidenceThe ScadaPro Server and Client applications fail to properly resolve file path links before performing file access operations. This insufficient path validation could allow a local attacker to manipulate file system links to access sensitive system files or escalate privileges, likely through symbolic link following or path traversal techniques.
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 dataall versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify ScadaPro Client installationSearch for ScadaPro Client executable or installation directory - common paths include C:\Program Files\Measuresoft\ScadaPro Client or check Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Measuresoft\ScadaProAffected if ScadaPro Client executable or installation directory is found on the system
-
Verify ScadaPro Server installationSearch for ScadaPro Server executable or installation directory - common paths include C:\Program Files\Measuresoft\ScadaPro Server or check Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Measuresoft\ScadaProAffected if ScadaPro Server executable or installation directory is found on the system
-
Check if ScadaPro services are runningOpen Windows Services console (services.msc) and look for ScadaPro Client or ScadaPro Server services, or run 'sc query' command to list running servicesAffected if A ScadaPro service is running on the system
-
Identify file access patterns in application logsReview ScadaPro application logs for file read/write operations, particularly looking for references to external file paths or unusual file access requestsAffected if Application logs show file access operations that could involve path traversal or symbolic link following
If either ScadaPro Client or Server is installed and running, the system is affected by this vulnerability since all versions are impacted.
Generated from the published advisory. Verify against your own configuration.
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 dataContact Measuresoft for vendor-supplied patches or security updates; if unavailable, implement network segmentation, restrict local user permissions, and apply compensating controls such as application whitelisting to limit file access capabilities.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2897 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-2897 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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