CVE-2022-0369
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 · uneditedTriangle MicroWorks SCADA Data Gateway Restore Workspace Directory Traversal Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Triangle MicroWorks SCADA Data Gateway. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed. The specific flaw exists within the Restore Workspace feature. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-17227.
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 confidenceA directory traversal vulnerability in the Restore Workspace feature of Triangle MicroWorks SCADA Data Gateway allows authenticated attackers to manipulate user-supplied file paths and write arbitrary files, achieving remote code execution as SYSTEM. Although authentication is required, the authentication mechanism can be bypassed.
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= 5.01.01CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Identify installed SCADA Data Gateway versionLocate the installation directory or check the application's About/Version information panel. Common locations include C:\Program Files\Triangle MicroWorks\SCADA Data Gateway or /opt/trianglemicroworks/. Use the application's built-in version check if available.Affected if The installed version is exactly 5.01.01 (this specific version is listed as affected)
-
Confirm Restore Workspace feature availabilityLocate and access the Restore Workspace feature within the SCADA Data Gateway management interface. This is typically found in the administration or workspace management section of the web-based or client interface.Affected if The Restore Workspace feature is present and accessible in the management interface (the vulnerability exists in this feature regardless of whether it has been used)
-
Verify management interface accessibilityDetermine if the SCADA Data Gateway management interface (typically HTTP/HTTPS on port 80, 443, or a custom port) is exposed to the network. Check firewall rules, network segmentation, and binding addresses in the configuration.Affected if The management interface is reachable from network segments other than trusted administrative networks, especially from untrusted or external networks (the authentication bypass makes remote exploitation possible)
-
Check for unauthorized artifactsReview file system directories that would be writable via directory traversal (commonly the installation directory, web root, or system directories). Look for unexpected files or scripts that may indicate prior exploitation.Affected if Unexpected files appear in directories outside expected workspace storage locations, or scripts/executables are found in web-accessible directories
Your environment is affected if you are running SCADA Data Gateway version 5.01.01 with the Restore Workspace feature accessible over a network where untrusted actors could reach the management interface.
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 dataApply vendor patch when available; if no patch exists, restrict network access to the SCADA Data Gateway management interface and consider disabling the Restore Workspace feature until remediation is possible.
- Consultation4.0 h
- Implementation8.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 $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0369 — 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-0369 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