CVE-2016-4523
Memory Safety in Trihedral Vtscada 8.0.05 – 11.2.02
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2016-4523 is a high-severity Out-of-bounds Read (CWE-125) vulnerability in Trihedral Vtscada. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 2% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
The vulnerability is an out-of-bounds read (CWE-125) in the WAP interface of Trihedral VTScada (formerly VTS) versions 8.x through 11.x prior to 11.2.02. It is rated 7.5 on CVSS 3.1 with a vector of AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H and can trigger an application crash.
Remote unauthenticated attackers can exploit the flaw over the network to cause a denial of service. The attack requires no user interaction and results only in loss of availability with no impact on confidentiality or integrity.
Public references include ICS-CERT advisory ICSA-16-159-01 and Zero Day Initiative advisory ZDI-16-405, which direct users to vendor updates addressing the issue. No information on observed in-the-wild exploitation is provided in the source data.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2016-5510
Vulnerability Data
The WAP interface in Trihedral VTScada (formerly VTS) 8.x through 11.x before 11.2.02 allows remote attackers to cause a denial of service (out-of-bounds read and application crash) via unspecified vectors.
- CWE(s)
- KEV Date Added
- 15 April 2022
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices such as bounds checking and memory-safe languages directly prevent out-of-bounds reads.
Vulnerability scanning and recording can discover instances of out-of-bounds reads after code is deployed.
Routine patching replaces vulnerable code containing out-of-bounds read flaws.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance includes fuzzing and static analysis that detect out-of-bounds read defects before release.
Logging can record evidence of an out-of-bounds read but does not prevent the weakness itself.
Secure development life cycle mandates input validation and bounds checking that directly prevent out-of-bounds reads.
Application security requirements include explicit bounds and memory-safety specifications that mitigate buffer over-reads.
Secure system architecture and engineering principles require memory-safe design patterns and runtime protections against out-of-bounds access.
Secure coding standards explicitly forbid unsafe pointer arithmetic and mandate bounds-checked reads, eliminating CWE-125.