A local buffer overflow vulnerability in Data Device Corporation dataSIMS Avionics ARINC 664-1 version 4.5.3 poses a severe risk of arbitrary code execution on affected Windows systems.

This is a stack-based buffer overflow (CWE-121) triggered by the application when it processes a specially crafted milstd1553result.txt file. An attacker with local access can manipulate this file to overwrite memory, potentially leading to arbitrary code execution with the privileges of the user running the software.

The exploitation of this vulnerability could allow an unauthorized local user to gain control over the host system, leading to a total compromise of system integrity and confidentiality. Given the specialized nature of avionics simulation software, such a breach could result in the corruption of critical testing data or unauthorized access to sensitive aerospace configuration files. With a CVSS score of 8.4, this vulnerability represents a high-risk security flaw that requires immediate attention in environments where this software is deployed.

Immediate Action: Users should update to the latest available version of the software provided by Data Device Corporation that addresses this memory corruption flaw.

Proactive Monitoring: Security teams should monitor file integrity for the milstd1553result.txt file and review system logs for signs of anomalous application crashes or unauthorized process execution.

Compensating Controls: Ensure that the software is executed with the least privilege necessary and restrict write access to the directory where the application processes its input files to prevent unauthorized file modification.

Public Exploit Available: Yes, a public proof-of-concept exists in the form of a Python script published on Exploit-DB (EDB-ID: 49577).

This vulnerability presents a clear risk to systems utilizing dataSIMS Avionics software. Organizations must prioritize updating the affected software to the vendor-patched version to eliminate the buffer overflow condition. If an update cannot be applied immediately, restrict access to the host system to trusted users only and implement strict file system permissions to prevent the placement of malicious input files.