CVE-2019-25319
Domain Quester · Domain Quester Pro
Domain Quester Pro 6.02 is vulnerable to a stack-based buffer overflow via the 'Domain Name Keywords' field, allowing remote attackers to execute arbitrary code by overwriting SEH registers.
Executive summary
Domain Quester Pro 6.02 is subject to a critical stack overflow vulnerability that enables remote attackers to execute arbitrary code and gain unauthorized system access via a bind shell.
Vulnerability
This vulnerability is a stack-based buffer overflow occurring within the 'Domain Name Keywords' input field. By overwriting Structured Exception Handler (SEH) registers, a remote, unauthenticated attacker can redirect application flow to execute a malicious payload, resulting in a bind shell on port 9999.
Business impact
A successful exploit grants the attacker full remote code execution (RCE) capabilities, leading to complete system compromise. With a CVSS score of 9.8, the risk is categorized as Critical, as it allows for the total loss of confidentiality, integrity, and availability of the host system. This could result in sensitive data exfiltration, the installation of ransomware, or the use of the server as a pivot point for further internal network attacks.
Remediation
Immediate Action: Administrators should immediately update Domain Quester Pro to the latest available version provided by the vendor to patch the overflow vulnerability.
Proactive Monitoring: Monitor network traffic for unusual activity on port 9999 and review system logs for access violations or unexpected application crashes related to the Domain Quester process.
Compensating Controls: Implement an Intrusion Prevention System (IPS) with signatures designed to detect SEH exploitation attempts and restrict network access to the application using a robust firewall.
Exploitation status
Public Exploit Available: No
Analyst recommendation
The critical nature of an SEH-based buffer overflow cannot be overstated, as it provides a direct path to system-level execution. Organizations must prioritize the decommissioning of version 6.02 or the application of vendor-supplied patches immediately to mitigate the risk of a full environment compromise.