Scada ServerApplication · Smartptt

CVE-2021-43938

CRITICAL · 9.8 CVSS v3.1 Published 2022-04-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Elcomplus SmartPTT SCADA Server is vulnerable to an unauthenticated user can request various files from the server without any authentication or authorization.

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 confidence

SmartPTT SCADA Server contains an unauthenticated arbitrary file disclosure vulnerability allowing remote attackers to request and retrieve sensitive files from the server filesystem without any authentication credentials. This critical path traversal issue exposes configuration files, credentials, and potentially operational data.

MitigationApply vendor patches if available; otherwise implement network segmentation to isolate the SCADA server, add or enforce authentication mechanisms for all endpoints, and deploy WAF rules to block directory traversal patterns.

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
Scada ServerApplication
Affected:= 1.4

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SmartPTT SCADA Server is installed
    Check running processes or installed services for SmartPTT SCADA Server components. Look for processes named 'SmartPTT' or 'scada' in task manager or via command: 'tasklist | findstr -i smartptt' or 'sc query type= service | findstr -i scada'
    Affected if SmartPTT SCADA Server is found running on the system
  2. Identify the installed version
    Locate the SmartPTT installation directory and check version information. Common locations include C:\Program Files\SmartPTT or C:\SmartPTT. Look for version.txt, about.exe, or right-click the executable and select Properties > Details for version info
    Affected if The installed version is exactly 1.4
  3. Determine if the web interface is exposed
    Check if the SmartPTT SCADA web interface is accessible. Test default ports typically used by SCADA web interfaces (commonly 8080, 8443, or 80/443). Use a browser or curl to attempt access: 'curl http://TARGET:PORT' where PORT is the configured SCADA web service port
    Affected if The SCADA web interface responds without requiring login credentials
  4. Check network exposure
    Evaluate whether the SCADA server is reachable from untrusted networks. Review firewall rules and network segmentation to determine if the web interface port is open to external or untrusted internal networks. Use 'netstat -an | findstr LISTENING' to identify listening ports
    Affected if The SCADA server web port is accessible from networks outside the trusted operational technology network

If SmartPTT SCADA Server version 1.4 is installed and its web interface is accessible without authentication from your network, your environment is affected by CVE-2021-43938.

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

Apply vendor patches if available; otherwise implement network segmentation to isolate the SCADA server, add or enforce authentication mechanisms for all endpoints, and deploy WAF rules to block directory traversal patterns.

Fix this in Scada Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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