dbcve.org
VtscadaApplication · Trihedral

CVE-2016-4532

CRITICAL · 9.1 CVSS v3.0 Published 2016-06-09
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
Directory traversal vulnerability in the WAP interface in Trihedral VTScada (formerly VTS) 8.x through 11.x before 11.2.02 allows remote attackers to read arbitrary files via a crafted pathname.

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

A directory traversal vulnerability exists in the WAP interface of Trihedral VTScada versions 8.x through 11.x before 11.2.02. Remote attackers can exploit this by sending crafted requests containing '..' sequences in file paths, allowing unauthorized read access to arbitrary files on the host system.

MitigationApply vendor patch (VTScada 11.2.02 or later) to resolve the directory traversal vulnerability. Until patched, restrict network access to the WAP interface to reduce exposure.

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
VtscadaApplication
Affected:= 10.1.05= 10.1.06= 10.1.07= 10.1.12= 9.0.02= 9.0.03= 9.0.08= 9.1.02= 9.1.03= 9.1.05= 9.1.09= 9.1.11

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
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Identify if Trihedral VTScada is installed
    Check for VTScada installation directory, service, or application binary. Common locations include C:\Program Files\Trihedral VTScada or C:\VTScada. Look for VTScada service in Windows Services or check for vtscada.exe process.
    Affected if VTScada software is found on the system
  2. Determine installed VTScada version
    Locate version information in the installation directory, typically in a version file, about dialog, or registry key under HKLM\Software\Trihedral\VTScada. The version is displayed in the application title bar when running.
    Affected if Installed version matches 8.x through 11.x before 11.2.02, or specifically 9.0.02, 9.0.03, 9.0.08, 9.1.02, 9.1.03, 9.1.05, 9.1.09, 9.1.11, 10.1.05, 10.1.06, 10.1.07, or 10.1.12
  3. Verify WAP interface is enabled
    Check if the WAP web interface service is running. Inspect VTScada configuration files or web service settings for WAP (typically port 80/443 or configured web server port). Confirm the web interface is accessible over network.
    Affected if WAP web interface is enabled and accessible externally
  4. Confirm vulnerability exposure
    Review network accessibility of the WAP interface. Determine if the WAP port is exposed to untrusted networks or the internet. Check firewall rules allowing external access to VTScada web ports.
    Affected if The WAP interface is network-accessible and version is in the affected range

The system is affected if Trihedral VTScada version 8.x through 11.x before 11.2.02 is installed with the WAP interface enabled and network-accessible.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch (VTScada 11.2.02 or later) to resolve the directory traversal vulnerability. Until patched, restrict network access to the WAP interface to reduce exposure.

Recommended fix Moderate confidence

VTScada 11.2.02 or later

  1. 1. Identify the current installed version of VTScada by checking the application or system information
  2. 2. Obtain VTScada version 11.2.02 or later from the official Trihedral vendor source
  3. 3. Review Trihedral VTScada upgrade documentation for your specific version
  4. 4. Back up the existing VTScada configuration and data according to backup procedures
  5. 5. Apply the upgrade to version 11.2.02 or later following vendor deployment instructions
  6. 6. Verify the WAP interface is functioning correctly after upgrade
  7. 7. Confirm the directory traversal vulnerability is resolved by testing with the patched version
Caveat Upgrading across major version jumps (e.g., 10.x to 11.x) may require testing of custom configurations and integrations; review vendor migration guide for compatibility notes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vtscada Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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