dbcve.org
Scadapro ServerApplication · Measuresoft

CVE-2024-3746

MEDIUM · 5.5 CVSS v3.1 Published 2024-04-30
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
The entire parent directory - C:\ScadaPro and its sub-directories and files are configured by default to allow user, including unprivileged users, to write or overwrite files.

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

The C:\ScadaPro directory and all subdirectories are configured with overly permissive NTFS access control lists (ACLs) that allow any user, including unprivileged users, write and overwrite permissions. This insecure default configuration could allow an attacker to replace executable files or configuration files, potentially leading to privilege escalation or arbitrary code execution when those files are accessed by higher-privileged users or services.

MitigationRestrict write permissions on C:\ScadaPro and its subdirectories to only authorized administrator and service accounts, removing write access for standard users and unprivileged accounts. Verify that application functionality is preserved after applying the corrected ACLs.

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:= 6.9.0.0

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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. Verify Scadapro Server installation exists
    Check if the C:\ScadaPro directory exists on the system using File Explorer or the command: dir C:\ScadaPro
    Affected if The C:\ScadaPro directory exists on the system
  2. Confirm Scadapro Server version
    Check the installed version of Measuresoft Scadapro Server. Look for version information in the program's installation directory, or check in Windows Programs and Features (Control Panel > Programs > Programs and Features) for 'Measuresoft Scadapro Server' version 6.9.0.0
    Affected if The installed version is exactly 6.9.0.0
  3. Examine NTFS permissions on ScadaPro root directory
    Right-click C:\ScadaPro in File Explorer, select Properties, go to the Security tab, and review the 'Users' group or 'Everyone' group permissions. Alternatively, run: icacls C:\ScadaPro to view all access control entries
    Affected if The Users group, Everyone, or standard user accounts are granted Write or Full Control permissions on C:\ScadaPro
  4. Examine NTFS permissions on ScadaPro subdirectories
    Run icacls C:\ScadaPro\* /t to recursively list permissions for all subdirectories and files within C:\ScadaPro, or manually inspect permissions on key subdirectories like bin, config, or data
    Affected if Any subdirectory under C:\ScadaPro grants Write or Full Control permissions to non-administrator users or the Everyone group
  5. Identify executable files vulnerable to replacement
    List executable files in C:\ScadaPro and its subdirectories using: dir C:\ScadaPro\*.exe /s /b. These files could be replaced by unprivileged users if write permissions allow it
    Affected if Executable files exist in directories where standard users have write access

A system is affected if Measuresoft Scadapro Server version 6.9.0.0 is installed and the C:\ScadaPro directory or its subdirectories grant write or full control permissions to standard users, the Users group, or the Everyone group.

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 write permissions on C:\ScadaPro and its subdirectories to only authorized administrator and service accounts, removing write access for standard users and unprivileged accounts. Verify that application functionality is preserved after applying the corrected ACLs.

Fix this in Scadapro Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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