PatchSiren cyber security CVE debrief
CVE-2016-5798 Fatek CVE debrief
CVE-2016-5798 describes buffer overflow conditions in Fatek Automation PM Designer V3 2.1.2.2, Automation FV Designer 1.2.8.0, and the Fatek Communication Server. According to the NVD record, an attacker can send additional valid packets to trigger a stack-based buffer overflow and crash, and can also trigger a remote buffer overflow on the communication server. NVD assigns a CVSS 3.0 score of 7.5 (HIGH) with network access, no privileges, no user interaction, and high availability impact.
- Vendor
- Fatek
- Product
- Unknown
- CVSS
- HIGH 7.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2016-07-17
- Original CVE updated
- 2025-06-05
- Advisory published
- 2016-07-17
- Advisory updated
- 2025-06-05
Who should care
Organizations that use Fatek Automation PM Designer V3 2.1.2.2, Automation FV Designer 1.2.8.0, or the Fatek Communication Server should review this issue. This is especially relevant for industrial control or automation environments where a crash could interrupt engineering or communications workflows.
Technical summary
The NVD entry identifies CWE-119 as the underlying weakness class. The vulnerable CPEs listed are cpe:2.3:a:fatek:automation_pm_designer:2.1.2.2 and cpe:2.3:a:fatek:automation_fv_designer:1.2.8.0. The vulnerability is network reachable (AV:N) and requires no privileges or user interaction (PR:N/UI:N). The reported effect is denial of service through stack-based or remote buffer overflow leading to a crash; the supplied corpus does not confirm code execution.
Defensive priority
High. The combination of network exposure, no authentication requirement, and high availability impact makes this a meaningful operational risk, even though the supplied corpus only confirms crash behavior.
Recommended defensive actions
- Identify whether any systems run Fatek Automation PM Designer V3 2.1.2.2, Automation FV Designer 1.2.8.0, or the Fatek Communication Server.
- Review the linked ICS-CERT advisory for vendor guidance and mitigation steps.
- Restrict network access to affected engineering and communication services to only trusted hosts and segments.
- Monitor affected systems for unexpected crashes or service interruptions.
- Apply any vendor-provided updates, mitigations, or compensating controls referenced in the advisory material.
- If the software is no longer needed on a host, remove or isolate it to reduce attack surface.
Evidence notes
This debrief is based only on the supplied NVD record and linked references. The NVD metadata lists the vulnerable Fatek versions, CWE-119, and the CVSS 3.0 vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. The description states that additional valid packets can trigger a stack-based buffer overflow and crash, and that a malicious attacker can trigger a remote buffer overflow on the Fatek Communication Server. Publication date used for timing context is 2017-02-13; the later modified date reflects record maintenance and not the original vulnerability date.
Sources and references
Verified primary and authoritative sources
-
CVE-2016-5798 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2016-5798
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2016-5798 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2016-5798
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://ics-cert.us-cert.gov/advisories/ICSA-16-287-06
[email protected] - Mitigation, Third Party Advisory, US Government Resource
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.