A timeout during a TLS handshake can result in the connection failing to terminate. This can result in a Niagara thread hanging and requires a manual restart of Niagara (Versions 4.6.96.28, 4.7.109.20, 4.7.110.32, 4.8.0.110) and Niagara Enterprise Security (Versions 2.4.31, 2.4.45, 4.8.0.35) to correct.
The code has a synchronous call to a remote resource, but there is no timeout for the call, or the timeout is set to infinite.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Niagara | Tridium | 4.6.96.28 (including) | 4.6.96.28 (including) |
| Niagara | Tridium | 4.7.109.20 (including) | 4.7.109.20 (including) |
| Niagara | Tridium | 4.7.110.32 (including) | 4.7.110.32 (including) |
| Niagara | Tridium | 4.8.0.110 (including) | 4.8.0.110 (including) |
| Niagara_enterprise_security | Tridium | 2.4.31 (including) | 2.4.31 (including) |
| Niagara_enterprise_security | Tridium | 2.4.45 (including) | 2.4.45 (including) |
| Niagara_enterprise_security | Tridium | 4.8.0.35 (including) | 4.8.0.35 (including) |
This issue can prevent the product from running reliably, since an outage for the remote resource can cause the product to hang. If the relevant code is reachable by an attacker, then this reliability problem might introduce a vulnerability.