S2OPC 1.7.3 contains a critical heap-based out-of-bounds write vulnerability that permits remote, unauthenticated attackers to execute arbitrary code.

The vulnerability exists in the server-side EventFilter handling during CreateMonitoredItems processing. By sending a crafted request, an unauthenticated remote attacker can trigger a heap-based out-of-bounds write, leading to arbitrary code execution.

This vulnerability is assigned a critical CVSS score of 9.8. Exploitation results in a total compromise of system confidentiality, integrity, and availability. Given that the attack is remote and unauthenticated, it presents an extreme risk to any environment utilizing S2OPC for industrial or secure communications.

Immediate Action: Update the S2OPC toolkit to the latest version provided by the vendor at the referenced GitHub advisory link to resolve the heap-based memory corruption.

Proactive Monitoring: Implement deep packet inspection (DPI) to monitor for malformed CreateMonitoredItems requests and alert on suspicious traffic directed at S2OPC services.

Compensating Controls: Use a Web Application Firewall or specialized industrial network security appliance to filter out malicious or malformed OPC UA traffic before it reaches the S2OPC server.

Public Exploit Available: Yes, a public proof-of-concept exists as documented in the vendor's security advisory.

The severity of this flaw and the availability of proof-of-concept code necessitate an immediate update. All systems utilizing S2OPC 1.7.3 must be patched or isolated from public-facing networks until the update is successfully applied to prevent potential remote exploitation.