Siemens SPPA-T3000 (Update A)
Specially crafted messages sent to the RPC service of the affected products could cause a Denial-of-Service condition on the remote and local communication functionality of the affected products. A reboot of the system is required to recover the remote and local communication functionality.

Please note that an attacker needs to have network access to the Application Server in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. The AdminService is available without authentication on the Application Server. An attacker can gain remote code execution by sending specifically crafted objects to one of its functions.

Please note that an attacker needs to have access to the Application Highway in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. The AdminService is available without authentication on the Application Server. An attacker can use methods exposed via this interface to receive password hashes of other users and to change user passwords.

Please note that an attacker needs to have access to the Application Highway in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. The RMI communication between the client and the Application Server is unencrypted. An attacker with access to the communication channel can read credentials of a valid user.

Please note that an attacker needs to have access to the Application Highway in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. The Application Server exposes directory listings and files containing sensitive information.

This vulnerability is independent from CVE-2019-18287.

Please note that an attacker needs to have access to the Application Highway in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. The Application Server exposes directory listings and files containing sensitive information.

This vulnerability is independent from CVE-2019-18286.

Please note that an attacker needs to have access to the Application Highway in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with valid authentication at the RMI interface could be able to gain remote code execution through an unsecured file upload.

Please note that an attacker needs to have access to the Application Highway in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server could trigger a Denial-of-Service condition and potentially gain remote code execution by sending specifically crafted packets to port 5010/tcp.

This vulnerability is independent from CVE-2019-18293, CVE-2019-18295, and CVE-2019-18296.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server could trigger a Denial-of-Service condition by sending specifically crafted packets to port 5010/tcp.

This vulnerability is independent from CVE-2019-18291, CVE-2019-18292, CVE-2019-18294, CVE-2019-18298, CVE-2019-18299, CVE-2019-18300, CVE-2019-18301, CVE-2019-18302, CVE-2019-18303, CVE-2019-18304, CVE-2019-18305, CVE-2019-18306, and CVE-2019-18307.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server could trigger a Denial-of-Service condition by sending specifically crafted packets to port 5010/tcp.

This vulnerability is independent from CVE-2019-18290, CVE-2019-18292, CVE-2019-18294, CVE-2019-18298, CVE-2019-18299, CVE-2019-18300, CVE-2019-18301, CVE-2019-18302, CVE-2019-18303, CVE-2019-18304, CVE-2019-18305, CVE-2019-18306, and CVE-2019-18307.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server could trigger a Denial-of-Service condition by sending specifically crafted packets to port 5010/tcp.

This vulnerability is independent from CVE-2019-18290, CVE-2019-18291, CVE-2019-18294, CVE-2019-18298, CVE-2019-18299, CVE-2019-18300, CVE-2019-18301, CVE-2019-18302, CVE-2019-18303, CVE-2019-18304, CVE-2019-18305, CVE-2019-18306, and CVE-2019-18307.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server could trigger a Denial-of-Service condition and potentially gain remote code execution by sending specifically crafted packets to port 5010/tcp.

This vulnerability is independent from CVE-2019-18289, CVE-2019-18295, and CVE-2019-18296.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server could trigger a Denial-of-Service condition by sending specifically crafted packets to port 5010/tcp.

This vulnerability is independent from CVE-2019-18290, CVE-2019-18291, CVE-2019-18292, CVE-2019-18298, CVE-2019-18299, CVE-2019-18300, CVE-2019-18301, CVE-2019-18302, CVE-2019-18303, CVE-2019-18304, CVE-2019-18305, CVE-2019-18306, and CVE-2019-18307.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server could trigger a Denial-of-Service condition and potentially gain remote code execution by sending specifically crafted packets to port 5010/tcp.

This vulnerability is independent from CVE-2019-18289, CVE-2019-18293, and CVE-2019-18296.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server could trigger a Denial-of-Service condition and potentially gain remote code execution by sending specifically crafted packets to port 5010/tcp.

This vulnerability is independent from CVE-2019-18289, CVE-2019-18293, and CVE-2019-18295.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with local access to the MS3000 Server and low privileges could gain root privileges by sending specifically crafted packets to a named pipe.

Please note that an attacker needs to have local access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server could trigger a Denial-of-Service condition by sending specifically crafted packets to port 5010/tcp.

This vulnerability is independent from CVE-2019-18290, CVE-2019-18291, CVE-2019-18292, CVE-2019-18294, CVE-2019-18299, CVE-2019-18300, CVE-2019-18301, CVE-2019-18302, CVE-2019-18303, CVE-2019-18304, CVE-2019-18305, CVE-2019-18306, and CVE-2019-18307.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server can trigger a Denial-of-Service condition by sending specifically crafted packets to port 5010/tcp.

This vulnerability is independent from CVE-2019-18290, CVE-2019-18291, CVE-2019-18292, CVE-2019-18294, CVE-2019-18298, CVE-2019-18300, CVE-2019-18301, CVE-2019-18302, CVE-2019-18303, CVE-2019-18304, CVE-2019-18305, CVE-2019-18306, and CVE-2019-18307.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server can trigger a Denial-of-Service condition by sending specifically crafted packets to port 5010/tcp.

This vulnerability is independent from CVE-2019-18290, CVE-2019-18291, CVE-2019-18292, CVE-2019-18294, CVE-2019-18298, CVE-2019-18299, CVE-2019-18301, CVE-2019-18302, CVE-2019-18303, CVE-2019-18304, CVE-2019-18305, CVE-2019-18306, and CVE-2019-18307.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server can trigger a Denial-of-Service condition by sending specifically crafted packets to port 5010/tcp.

This vulnerability is independent from CVE-2019-18290, CVE-2019-18291, CVE-2019-18292, CVE-2019-18294, CVE-2019-18298, CVE-2019-18299, CVE-2019-18300, CVE-2019-18302, CVE-2019-18303, CVE-2019-18304, CVE-2019-18305, CVE-2019-18306, and CVE-2019-18307.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server can trigger a Denial-of-Service condition by sending specifically crafted packets to port 5010/tcp.

This vulnerability is independent from CVE-2019-18290, CVE-2019-18291, CVE-2019-18292, CVE-2019-18294, CVE-2019-18298, CVE-2019-18299, CVE-2019-18300, CVE-2019-18301, CVE-2019-18303, CVE-2019-18304, CVE-2019-18305, CVE-2019-18306, and CVE-2019-18307.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server can trigger a Denial-of-Service condition by sending specifically crafted packets to port 5010/tcp.

This vulnerability is independent from CVE-2019-18290, CVE-2019-18291, CVE-2019-18292, CVE-2019-18294, CVE-2019-18298, CVE-2019-18299, CVE-2019-18300, CVE-2019-18301, CVE-2019-18302, CVE-2019-18304, CVE-2019-18305, CVE-2019-18306, and CVE-2019-18307.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server can trigger a Denial-of-Service condition by sending specifically crafted packets to port 5010/tcp.

This vulnerability is independent from CVE-2019-18290, CVE-2019-18291, CVE-2019-18292, CVE-2019-18294, CVE-2019-18298, CVE-2019-18299, CVE-2019-18300, CVE-2019-18301, CVE-2019-18302, CVE-2019-18303, CVE-2019-18305, CVE-2019-18306, and CVE-2019-18307.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server could trigger a Denial-of-Service condition by sending specifically crafted packets to port 5010/tcp.

This vulnerability is independent from CVE-2019-18290, CVE-2019-18291, CVE-2019-18292, CVE-2019-18294, CVE-2019-18298, CVE-2019-18299, CVE-2019-18300, CVE-2019-18301, CVE-2019-18302, CVE-2019-18303, CVE-2019-18304, CVE-2019-18306, and CVE-2019-18307.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server could trigger a Denial-of-Service condition by sending specifically crafted packets to port 5010/tcp.

This vulnerability is independent from CVE-2019-18290, CVE-2019-18291, CVE-2019-18292, CVE-2019-18294, CVE-2019-18298, CVE-2019-18299, CVE-2019-18300, CVE-2019-18301, CVE-2019-18302, CVE-2019-18303, CVE-2019-18304, CVE-2019-18305, and CVE-2019-18307.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server could trigger a Denial-of-Service condition by sending specifically crafted packets to port 5010/tcp.

This vulnerability is independent from CVE-2019-18290, CVE-2019-18291, CVE-2019-18292, CVE-2019-18294, CVE-2019-18298, CVE-2019-18299, CVE-2019-18300, CVE-2019-18301, CVE-2019-18302, CVE-2019-18303, CVE-2019-18304, CVE-2019-18305, and CVE-2019-18306.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with local access to the MS3000 Server and a low privileged user account could gain root privileges by manipulating specific files in the local file system.

This vulnerability is independent from CVE-2019-18309.

Please note that an attacker needs to have local access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with local access to the MS3000 Server and a low privileged user account could gain root privileges by manipulating specific files in the local file system.

This vulnerability is independent from CVE-2019-18308.

Please note that an attacker needs to have local access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server could trigger a Denial-of-Service condition by sending specifically crafted packets to port 7061/tcp.

This vulnerability is independent from CVE-2019-18311.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server could trigger a Denial-of-Service condition by sending specifically crafted packets to port 7061/tcp.

This vulnerability is independent from CVE-2019-18310.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server could be able to enumerate running RPC services.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server could gain remote code execution by sending specifically crafted objects to one of the RPC services.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the Application Server could gain remote code execution by sending specifically crafted objects via RMI.

Please note that an attacker needs to have network access to the Application Server in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the Application Server could gain remote code execution by sending specifically crafted packets to 8888/tcp.

Please note that an attacker needs to have network access to the Application Server in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the Application Server could gain remote code execution by sending specifically crafted packets to 1099/tcp.

Please note that an attacker needs to have network access to the Application Server in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the Application Server could cause a Denial-of-Service condition by sending specifically crafted objects via RMI.

This vulnerability is independent from CVE-2019-18318 and CVE-2019-18319.

Please note that an attacker needs to have network access to the Application Server in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the Application Server can cause a Denial-of-Service condition by sending specifically crafted objects via RMI.

This vulnerability is independent from CVE-2019-18317 and CVE-2019-18319.

Please note that an attacker needs to have network access to the Application Server in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the Application Server could cause a Denial-of-Service condition by sending specifically crafted objects via RMI.

This vulnerability is independent from CVE-2019-18317 and CVE-2019-18318.

Please note that an attacker needs to have network access to the Application Server in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the Application Server could be able to upload arbitrary files without authentication.

Please note that an attacker needs to have network access to the Application Server in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server could be able to read and write arbitrary files on the local file system by sending specifically crafted packets to port 5010/tcp.

This vulnerability is independent from CVE-2019-18322.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server could be able to read and write arbitrary files on the local file system by sending specifically crafted packets to port 5010/tcp.

This vulnerability is independent from CVE-2019-18321.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server could cause a Denial-of-Service condition and potentially gain remote code execution by sending specifically crafted packets to 5010/tcp.

This vulnerability is independent from CVE-2019-18324, CVE-2019-18325, CVE-2019-18326, CVE-2019-18327, CVE-2019-18328, CVE-2019-18329, and CVE-2019-18330.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server can cause a Denial-of-Service condition and potentially gain remote code execution by sending specifically crafted packets to 5010/tcp.

This vulnerability is independent from CVE-2019-18323, CVE-2019-18325, CVE-2019-18326, CVE-2019-18327, CVE-2019-18328, CVE-2019-18329, and CVE-2019-18330.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server can cause a Denial-of-Service condition and potentially gain remote code execution by sending specifically crafted packets to 5010/tcp.

This vulnerability is independent from CVE-2019-18323, CVE-2019-18324, CVE-2019-18326, CVE-2019-18327, CVE-2019-18328, CVE-2019-18329, and CVE-2019-18330.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server can cause a Denial-of-Service condition and potentially gain remote code execution by sending specifically crafted packets to 5010/tcp.

This vulnerability is independent from CVE-2019-18323, CVE-2019-18324, CVE-2019-18325, CVE-2019-18327, CVE-2019-18328, CVE-2019-18329, and CVE-2019-18330.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server can cause a Denial-of-Service condition and potentially gain remote code execution by sending specifically crafted packets to 5010/tcp.

This vulnerability is independent from CVE-2019-18323, CVE-2019-18324, CVE-2019-18325, CVE-2019-18326, CVE-2019-18328, CVE-2019-18329, and CVE-2019-18330.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server can cause a Denial-of-Service condition and potentially gain remote code execution by sending specifically crafted packets to 5010/tcp.

This vulnerability is independent from CVE-2019-18323, CVE-2019-18324, CVE-2019-18325, CVE-2019-18326, CVE-2019-18327, CVE-2019-18329, and CVE-2019-18330.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server can cause a Denial-of-Service condition and potentially gain remote code execution by sending specifically crafted packets to 5010/tcp.

This vulnerability is independent from CVE-2019-18323, CVE-2019-18324, CVE-2019-18325, CVE-2019-18326, CVE-2019-18327, CVE-2019-18328, and CVE-2019-18330.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the MS3000 Server could cause a Denial-of-Service condition and potentially gain remote code execution by sending specifically crafted packets to 5010/tcp.

This vulnerability is independent from CVE-2019-18323, CVE-2019-18324, CVE-2019-18325, CVE-2019-18326, CVE-2019-18327, CVE-2019-18328, and CVE-2019-18329.

Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the Application Server could gain access to path and filenames on the server by sending specifically crafted packets to 1099/tcp.

Please note that an attacker needs to have network access to the Application Server in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the Application Server could gain access to directory listings of the server by sending specifically crafted packets to 80/tcp, 8095/tcp or 8080/tcp.

Please note that an attacker needs to have network access to the Application Server in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the Application Server could gain access to filenames on the server by sending specifically crafted packets to 8090/tcp.

Please note that an attacker needs to have network access to the Application Server in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the Application Server could be able to enumerate valid user names by sending specifically crafted packets to 8090/tcp.

Please note that an attacker needs to have network access to the Application Server in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known. An attacker with network access to the Application Server could be able to gain access to logs and configuration files by sending specifically crafted packets to 80/tcp.

Please note that an attacker needs to have network access to the Application Server in order to exploit this vulnerability.

At the time of advisory publication no public exploitation of this security vulnerability was known.