Tal Keren

The issue allows a remote attacker to potentially exploit heap corruption via a crafted web app, due to a use after free in the Network component. The severity of this issue is classified as Medium by Chromium.

The issue is related to incorrect code generation management in the programmable logic controllers' firmware. An attacker with administrator access on a workstation running Studio 5000 Logix Designer could inject controller code that is undetectable to a user. This could allow an attacker to embed controller code that a user cannot detect.

The issue allows an attacker to modify user program code on certain control systems. This is possible because the Studio 5000 Logix Designer writes user-readable program code to a separate location than the executed compiled code, enabling an attacker to change one without affecting the other. The vulnerability is related to the possibility of injecting functionality from an untrusted management environment, which can be exploited by a remote attacker to execute arbitrary code by modifying byte code.

The issue is related to the lack of validation of a key-value field in the Splunk-to-Splunk protocol, resulting in a denial-of-service in Splunk Enterprise instances configured to index Universal Forwarder traffic. It does not impact Universal Forwarders. When Splunk forwarding is secured using TLS or a Token, the attack requires compromising the certificate or token, or both. Implementation of either or both reduces the severity to Medium.