Siemens has workarounds and mitigations available to handle multiple vulnerabilities in its TIM 4R-IE, according to a report with CISA.
The remotely exploitable vulnerabilities are incorrect type conversion or cast, improper input validation, improper authentication, security features, null pointer dereference, data processing errors, exposure of sensitive information to an unauthorized actor, and a race condition.
Successful exploitation of these vulnerabilities, which Siemens self-reported, could compromise the confidentiality, integrity, and availability of the device.
The following TIM 4R-IE communication modules suffer from the vulnerabilities:
- TIM 4R-IE (incl. SIPLUS NET variants): All versions
- TIM 4R-IE DNP3 (incl. SIPLUS NET variants): All versions
In one vulnerability, the ULOGTOD function in ntp.d in SNTP before 4.2.7p366 does not properly perform type conversions from a precision value to a double, which allows remote attackers to cause a denial of service (infinite loop) via a crafted NTP packet.
CVE-2015-5219 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 7.5.
In addition, the decodenetnum function in ntpd in NTP 4.2.x before 4.2.8p4 and 4.3.x before 4.3.77 allows remote attackers to cause a denial of service (assertion failure) via a 6 or mode 7 packet containing a long data value.
CVE-2015-7855 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 6.5.
Also, crypto-NAK packets in ntpd in NTP 4.2.x before 4.2.8p4 and 4.3.x before 4.3.77 allows remote attackers to bypass authentication.
CVE-2015-7871 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 9.8.
In another issue, NTP before 4.2.8p6 and 4.3.x before 4.3.90, when configured in broadcast mode, allows man-in-the-middle attackers to conduct replay attacks by sniffing the network.
CVE-2015-7973 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 6.5.
In addition, NTP 4.x before 4.2.8p6 and 4.3.x before 4.3.90 do not verify peer associations of symmetric keys when authenticating packets, which might allow remote attackers to conduct impersonation attacks via an arbitrary trusted key, aka a “skeleton key.”
CVE-2015-7974 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 7.7.
Also, ntpd in NTP before 4.2.8p6 and 4.3.x before 4.3.90 allows remote attackers to cause a denial of service (NULL pointer dereference) via a ntpdc reslist command.
CVE-2015-7977 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 5.9.
In another issues, NTP before 4.2.8p6 and 4.3.x before 4.3.90 allows remote attackers to cause a denial of service (client-server association tear down) by sending broadcast packets with invalid authentication to a broadcast client.
CVE-2015-7979 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 7.5.
In addition, the rate limiting feature in NTP 4.x before 4.2.8p4 and 4.3.x before 4.3.77 allows remote attackers to have unspecified impact via a large number of crafted requests.
CVE-2015-7705 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 9.8.
Also, NTP before 4.2.8p6 and 4.3.x before 4.3.90 allows remote attackers to bypass the origin timestamp validation via a packet with an origin timestamp set to zero.
CVE-2015-8138 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 5.3.
In another issue, an off-path attacker can cause a preemptible client association to be demobilized in NTP 4.2.8p4 and earlier and NTPSec a5fb34b9cc89b92a8fef2f459004865c93bb7f92 by sending a crypto NAK packet to a victim client with a spoofed source address of an existing associated peer. This is true even if authentication is enabled.
CVE-2016-1547 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 5.3.
In addition, an attacker can spoof a packet from a legitimate ntpd server with an origin timestamp that matches the peer->dst timestamp recorded for that server. After making this switch, the client in NTP 4.2.8p4 and earlier and NTPSec aa48d001683e5b791a743ec9c575aaf7d867a2b0c will reject all future legitimate server responses. It is possible to force the victim client to move time after the mode has been changed. ntpq gives no indication that the mode has been switched.
CVE-2016-1548 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 7.2.
Also, an exploitable vulnerability exists in the message authentication functionality of libntp in ntp 4.2.8p4 and NTPSec a5fb34b9cc89b92a8fef2f459004865c93bb7f92. An attacker can send a series of crafted messages to attempt to recover the message digest key.
CVE-2016-1550 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 5.3.
In another issue, ntpd in NTP 4.x before 4.2.8p8 allows remote attackers to cause a denial of service (ephemeralassociation demobilization) by sending a spoofed crypto-NAK packet with incorrect authentication data at a certain time.
CVE-2016-4953 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 7.5.
In addition, the process_packet function in ntp_proto.c in ntpd in NTP 4.x before 4.2.8p8 allows remote attackers to cause a denial of service (peer-variable modification) by sending spoofed packets from many source IP addresses in a certain scenario, as demonstrated by triggering an incorrect leap indication.
CVE-2016-4954 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 7.5.
The product sees use mainly in the critical manufacturing sector, and on a global basis.
No known public exploits specifically target these vulnerabilities. However, an attacker with low skill level could leverage these low complexity vulnerabilities.
Siemens identified the following workarounds and mitigations users can apply to reduce the risk:
- Deactivate NTP-based time synchronization of the device, if enabled. The feature is disabled by default.
- Configure an additional firewall to prevent communication to the Port UDP/123 of an affected device.
- Migrate to a successor product.
As a general security measure, Siemens recommends protecting network access to devices with appropriate mechanisms. In order to operate the devices in a protected IT environment, Siemens recommends configuring the environment according to Siemens Operational Guidelines for Industrial Security and following the recommendations in the product manuals.
For additional information, click on Siemens Security Advisory SSA-497656.

