A local buffer overflow vulnerability in FlexHEX 2.71 allows an attacker to achieve arbitrary code execution on the host system.

The application is susceptible to a local buffer overflow within the Stream Name dialog box. By providing a specially crafted string that triggers a structured exception handler (SEH) overflow, a local, unauthenticated attacker can execute arbitrary code on the underlying Windows system.

This vulnerability carries a high severity, as indicated by the CVSS score of 8.4. Successful exploitation allows for complete system compromise, enabling an attacker to gain full control over the host machine, install malicious software, or access sensitive local data. Given the nature of the exploit, this could lead to significant data loss or unauthorized administrative access within the local environment.

Immediate Action: As there is no official patch available from the vendor, users should exercise extreme caution when opening untrusted files or interacting with the Stream Name dialog in FlexHEX. If the software is not mission-critical, it is recommended to uninstall the application until a security update is provided.

Proactive Monitoring: Security teams should monitor endpoint logs for suspicious process spawning, such as unexpected instances of calc.exe or other common payloads, following interactions with the FlexHEX software.

Compensating Controls: Implement endpoint protection solutions that can detect and block buffer overflow attempts or unauthorized memory manipulation at the process level.

Public Exploit Available: Yes, a functional proof-of-concept exploit exists and is documented in the Exploit-DB entry 46665.

The presence of a publicly available exploit for this local buffer overflow significantly increases the risk to any system running FlexHEX 2.71. Organizations must prioritize the identification and removal or restriction of this software on all workstations. Until a vendor-supplied patch is released, users must treat the application as untrusted and avoid inputting external or unverified data into the affected fields.