CVE-2023-39462
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 Workspace Unrestricted Upload Vulnerability. This vulnerability allows remote attackers to upload arbitrary files 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 processing of workspace files. The issue results from the lack of proper validation of user-supplied data, which can allow the upload of arbitrary files. An attacker can leverage this in conjunction with other vulnerabilitites to execute arbitrary code in the context of root. Was ZDI-CAN-20536.
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 confidenceTriangle MicroWorks SCADA Data Gateway contains an unrestricted file upload vulnerability in workspace file processing. The application fails to properly validate user-supplied data during workspace file uploads, allowing attackers to upload arbitrary files. Although authentication is required, the authentication mechanism can be bypassed, and this vulnerability can be chained with other flaws to achieve arbitrary code execution as root.
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.1.3.20324CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed SCADA Data Gateway versionCheck the installed version of Triangle MicroWorks SCADA Data Gateway using the product's built-in version information, typically found in the application properties, about dialog, or via command line tools provided by the productAffected if The installed version matches exactly 5.1.3.20324
-
Verify workspace file upload feature accessibilityDetermine if the workspace file upload functionality is exposed and accessible to users. This may involve checking web interface endpoints, API paths related to workspace file handling, or application configuration that enables this featureAffected if The workspace file upload endpoint is accessible without proper access controls or the feature is enabled in the configuration
-
Confirm authentication mechanism is presentInspect the authentication configuration for the workspace file upload functionality to verify whether authentication is properly enforced. Check for authentication bypass vulnerabilities in the login or session management mechanismAffected if Authentication can be bypassed or is not properly validating requests to the workspace upload functionality
-
Check uploaded file storage locationExamine where uploaded workspace files are stored on the filesystem. Verify if they are placed in directories with executable permissions or are accessible via web-serving pathsAffected if Uploaded files are stored in directories that allow execution or are web-accessible without sanitization
You are affected if the installed version is exactly 5.1.3.20324 AND the workspace file upload feature is accessible with either bypassable authentication or files stored in executable locations.
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 dataImplement strict validation of workspace file uploads, including file type verification, content inspection, and storage in non-executable directories. Additionally, fix the authentication bypass vulnerability and restrict uploaded file execution privileges.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39462 — 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-2023-39462 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