SEH Buffer Overflow in AIDA64 Business 5.99.4900
CVE-2019-25631 is a structured exception handling (SEH) buffer overflow vulnerability in AIDA64 Business 5.99.4900. The flaw is triggered via the SMTP display name field exposed through the application's preferences or report wizard functionality. An attacker can supply crafted input containing egg hunter shellcode and overwrite SEH pointers, resulting in redirection of execution flow to attacker-controlled payloads. Successful exploitation yields arbitrary code execution in the context of the AIDA64 Business application.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows arbitrary code execution with the privileges of the vulnerable AIDA64 Business process. Given the assigned impact metrics, compromise can result in high confidentiality, integrity, and availability impact, including execution of attacker-supplied payloads, modification of local data accessible to the application, and potential disruption of the application or host environment reachable with those privileges.
If you can’t patch tonight, do this now.
Until a fixed version is deployed, restrict local access to systems running AIDA64 Business 5.99.4900, especially by untrusted users. Avoid using or populating the SMTP display name field in preferences or report wizard workflows with untrusted input. Where possible, apply application control, exploit mitigations such as DEP/ASLR/SEHOP if supported and effective in the environment, and monitor for abnormal crashes or exploit attempts involving the affected input fields.
Patch, then assume compromise.
Upgrade from AIDA64 Business 5.99.4900 to a fixed version if one is available from the vendor. If no patched release is currently identified in the provided content, organizations should obtain vendor guidance from AIDA64 and avoid continued use of the affected version in exposed or untrusted workflows. Validate that any updated release fully addresses the unsafe handling of the SMTP display name field in preferences and report wizard code paths.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.