CVE-2022-3263
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 · uneditedThe security descriptor of Measuresoft ScadaPro Server version 6.7 has inconsistent permissions, which could allow a local user with limited privileges to modify the service binary path and start malicious commands with SYSTEM privileges.
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 · high confidenceMeasuresoft ScadaPro Server version 6.7 contains a service configuration vulnerability where the security descriptor for the service has inconsistent or weak permissions. A local user with limited privileges can modify the service binary path, allowing them to point the service to a malicious executable that will execute with SYSTEM-level privileges.
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= 6.7CVSS 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 Server service is presentOpen Windows Services console (services.msc) or run 'sc query ScadaProServer' to list the ScadaPro Server serviceAffected if No ScadaPro Server service is found - not affected if service does not exist
-
Identify ScadaPro Server versionCheck the executable path of the ScadaPro Server service (via 'sc qc ScadaProServer' or Properties in Services console) and query its version property, or check the version from the binary at the reported pathAffected if Installed version is 6.7 - vulnerability is present at this specific version
-
Query service binary path configurationRun 'sc qc ScadaProServer' or use PowerShell Get-WmiObject -Class Win32_Service -Filter "Name='ScadaProServer'" to retrieve the binary pathAffected if Binary path points to an executable that can be identified and examined for permission issues
-
Check permissions on service binary pathRight-click the executable file in the binary path, go to Properties > Security tab, or run icacls <path_to_executable> to view ACLsAffected if Users with limited or non-admin privileges have Write, Write DAC, or Full Control permissions on the service binary or its containing folder, allowing path modification
-
Check service configuration write permissionsRun 'sc sdset ScadaProServer' to view the security descriptor, or use accesschk.exe (Sysinternals) with 'accesschk.exe -cvc ScadaProServer' to check who can reconfigure the serviceAffected if Non-administrator users are granted SERVICE_CHANGE_CONFIG or WRITE_DAC access, enabling modification of the binary path
A user is affected if ScadaPro Server version 6.7 is installed and non-privileged users can modify the service binary path or its containing folder permissions.
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 dataCorrect the service binary path permissions to restrict modification to administrators only, audit other services for similar permission issues, and consider running the ScadaPro Server service with a least-privilege service account rather than SYSTEM if the application architecture permits.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2022-3263 — 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-3263 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