A critical stack-based buffer overflow in SIPP 3.3 allows local unauthenticated attackers to achieve arbitrary code execution by supplying oversized values within a configuration file.

The application fails to perform adequate bounds checking when parsing configuration files, leading to a stack-based buffer overflow. An unauthenticated local attacker can leverage this flaw to overwrite the return address and execute arbitrary code via return-oriented programming gadgets.

The ability to execute arbitrary code on a server facilitates full system compromise, potentially leading to unauthorized data access, lateral movement within the network, or total system disruption. Given the CVSS score of 8.4, this vulnerability represents a high-severity risk that could be utilized to gain persistent control over affected traffic generation infrastructure.

Immediate Action: Since no official patch is currently identified, restrict access to the configuration files and the application execution environment to trusted users only.

Proactive Monitoring: Monitor system logs for unexpected application crashes or execution of shell processes initiated by the SIPP service, which may indicate exploitation attempts.

Compensating Controls: Implement strict file system permissions on configuration directories to ensure only authorized administrative accounts can modify or supply configuration files to the application.

Public Exploit Available: Yes — a public proof-of-concept exploit is available via the Exploit-DB entry 45288.

The presence of a publicly available exploit for this buffer overflow creates a significant risk for environments utilizing SIPP 3.3. Security teams must prioritize restricting local access to the application and its configuration files immediately, as the lack of a vendor-supplied patch necessitates rigorous manual access control to prevent unauthorized code execution.