CVE-2022-2895
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 (All Versions) uses unmaintained ActiveX controls. These controls may allow two stack-based buffer overflow instances 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 confidenceMeasuresoft ScadaPro Server contains two stack-based buffer overflow vulnerabilities in unmaintained ActiveX controls when processing specific project files. The flaws stem from legacy ActiveX components that are no longer actively maintained by the vendor, potentially allowing remote code execution or service disruption.
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 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm ScadaPro Server installationSearch for 'ScadaPro' in installed programs (Control Panel > Programs and Features) or check for ScadaPro-related services running on the system using 'sc query' or Services.mscAffected if ScadaPro Server is installed or running on the system
-
Identify ActiveX componentsCheck Windows registry under HKLM\SOFTWARE\Microsoft\Code Store Database\Distribution Units or HKCU\SOFTWARE\Classes for ActiveX controls related to Measuresoft or ScadaPro. Use 'reg query' commands or a registry viewer.Affected if ActiveX controls belonging to Measuresoft ScadaPro are registered on the system
-
Locate ScadaPro project filesSearch the filesystem for project file extensions commonly used by SCADA systems (such as .spj, .spd, .xml, or proprietary formats) in directories where ScadaPro stores project data. Check default installation directories and user data folders.Affected if ScadaPro project files exist on the system and the software processes them
-
Verify service exposureCheck network listening ports on the server using 'netstat -an' or review firewall rules to determine if ScadaPro Server services are accessible from network segments. Review SCADA-specific ports if documented by the vendor.Affected if ScadaPro Server is reachable over the network, increasing exposure to remote exploitation
-
Review ActiveX control usageExamine event logs (Windows Event Viewer) under Application and System logs for errors or warnings related to ActiveX controls or ScadaPro components. Also check IIS or web server logs if ScadaPro has a web interface.Affected if Logs show ActiveX controls are being loaded or executed by the application
If Measuresoft ScadaPro Server is installed with its ActiveX controls present and processing project files, the environment is affected by this vulnerability since all versions contain the unmaintained vulnerable components.
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 dataSince the affected ActiveX controls are unmaintained, prioritize network segmentation to isolate the ScadaPro Server and implement compensating controls such as input validation at network boundaries. Consider migrating to actively-supported SCADA software if the vendor cannot provide a patch.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2895 — 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-2895 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