A stack-based buffer overflow in Weird Solutions BOOTP Turbo 2.0 allows an unauthenticated attacker to crash the application via a malicious payload.

This vulnerability is a stack-based buffer overflow (CWE-121) triggered when the application processes a crafted input of 2196 bytes, which overwrites the Structured Exception Handler (SEH). The attacker requires no authentication to interact with the vulnerable logging input field, leading to an application crash and potential corruption of the SEH chain.

The primary risk posed by this vulnerability is the disruption of critical network services provided by the BOOTP Turbo application. Because the software is designed to handle boot configuration protocols, a successful denial of service attack could prevent client systems from correctly booting or obtaining network configurations. With a CVSS score of 7.5, the vulnerability represents a significant risk to availability, though it does not inherently grant remote code execution capabilities based on current evidence.

Immediate Action: As there is no official patch currently documented for this legacy software, administrators should restrict access to the BOOTP Turbo management interface to authorized personnel only.

Proactive Monitoring: Monitor system event logs for repeated application crashes or service restarts that may indicate an ongoing attempt to exploit the SEH corruption flaw.

Compensating Controls: Deploy host-based intrusion prevention systems or endpoint security solutions configured to detect and block malformed input patterns directed at the BOOTP Turbo binary.

Public Exploit Available: Yes, a proof-of-concept exists and is documented in the Exploit Database (EDB-ID: 47955).

Given the availability of a public proof-of-concept and the lack of a vendor-provided patch, users should consider this software end-of-life or highly vulnerable. Organizations should prioritize replacing BOOTP Turbo with a modern, supported alternative to eliminate the risk of service disruption. If the software must remain in production, it should be isolated within a restricted network segment with strictly enforced access controls.