**CVE-2020-14483** is a denial-of-service flaw in Tridium Niagara 4.6 to 4.8 and Niagara Enterprise Security 2.4 and 4.8, published by NVD on 2020-08-13: a timeout during a TLS handshake leaves the connection open, so a Niagara thread hangs until someone restarts Niagara by hand. NVD scores it 4.3; it is fixed in Niagara 4.9.
Vulnerability summary
CVSS base score
4.3
Medium severity
EPSS score (FIRST)
0.4%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2020-14483 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Tridium Niagara 4 | cpe:2.3:a:tridium:niagara:*:*:*:*:*:*:*:* | NVD: 4.6.96.28, 4.7.109.20, 4.7.110.32, 4.8.0.110; fixed in 4.9.0.198 (SB 2020-Tridium-2) |
| Tridium Niagara Enterprise Security | cpe:2.3:a:tridium:niagara_enterprise_security:*:*:*:*:*:*:*:* | NVD: 2.4.31, 2.4.45, 4.8.0.35; fixed in 4.9.0.60 (SB 2020-Tridium-2) |
What does this mean for affected devices?
NVD's description reads: "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" and lists Niagara 4.6.96.28, 4.7.109.20, 4.7.110.32 and 4.8.0.110 and Niagara Enterprise Security 2.4.31, 2.4.45 and 4.8.0.35 (NVD). NVD's own CVSS 3.1 score is 4.3 with vector CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L: an attacker on an adjacent network, no privileges, low availability impact. NVD's CVSS v2 score is 3.3. NVD records NVD-CWE-Other; CISA's advisory uses CWE-1088, synchronous access of a remote resource without timeout.
Tridium's bulletin SB 2020-Tridium-2 of July 2020 states that "Niagara 4.6, 4.7 and 4.8 and Niagara EntSec 2.4 and 4.8 have a TLS timeout issue that could cause a Niagara thread to hang indefinitely. This has been fixed in Niagara 4.9 and EntSec 4.9," with update versions 4.9.0.198 and 4.9.0.60, and asks "all Niagara customers for all supported platforms" to update. CISA republished it as ICSA-20-224-03 on 2020-08-11 (CSAF), names Commercial Facilities, Critical Manufacturing, Government Facilities and Information Technology as sectors, and says "No known public exploits specifically target this vulnerability."
The bug sits on the encrypted path that Niagara hardening pushes sites towards. The Niagara 4 Hardening Guide tells administrators to set FoxS Enabled and FoxS Only to true, which moves Fox onto TLS on port 4911, so on a hardened station TLS handshakes are the normal way in. A station whose thread hangs needs a person to restart it, which on a JACE controller in a plant room can mean a site visit. Tridium's end-of-life update adds a hardware reason to move off these releases: from November 1, 2022, JACE 8000 "versions below 4.9u1 will not be supported with new JACE licenses and SD cards."
CVE-2020-14483 is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.0044, percentile 38.6, in the 2026-11-15 dataset (CISA KEV, FIRST EPSS).
Upgrade to Niagara 4.9.0.198 or Enterprise Security 4.9.0.60 or later; any current 4.14 or 4.15 release is well past the fix. The bulletin's interim steps are to review who can authenticate, limit physical access including the Ethernet port, and use a VPN for remote connections. Our Niagara Fox protocol guide covers why FoxS needs patching as well as enabling, CVE-2025-3943 is a 2025 Niagara bug that also depends on unencrypted traffic, and CVE-2012-4701 is a Niagara AX flaw from the older code line.
Evidence
- TLS handshake timeout leaves connection open, Niagara thread hangs, manual restart; versions 4.6.96.28, 4.7.109.20, 4.7.110.32, 4.8.0.110 and EntSec 2.4.31, 2.4.45, 4.8.0.35; NVD Primary CVSS 3.1 4.3 (AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L), v2 3.3; NVD-CWE-Other; published 2020-08-13. — NVD
- Niagara 4.6-4.8 and EntSec 2.4/4.8 affected, fixed in Niagara 4.9 (4.9.0.198) and EntSec 4.9 (4.9.0.60); all supported platforms should update; mitigations; July 2020. — Honeywell/Tridium Security Bulletin SB 2020-Tridium-2: Niagara TLS timeout vulnerability (PDF)
- ICSA-20-224-03 of 2020-08-11: CWE-1088, CVSS 4.3; sectors Commercial Facilities, Critical Manufacturing, Government Facilities, Information Technology; no known public exploits. — CISA ICSA-20-224-03: Tridium Niagara (CSAF)
- Set FoxS Enabled and FoxS Only to true; FoxS port defaults to 4911. — Tridium: Niagara 4 Hardening Guide (2025-01-17, PDF)
- From November 1, 2022, JACE 8000 versions below 4.9u1 are not supported with new JACE licenses and SD cards. — Tridium: Niagara AX end-of-life update
- Not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). — CISA KEV
- EPSS 0.00438 (percentile 38.6), dataset 2026-11-15, read 2026-11-16. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
What happens when CVE-2020-14483 is triggered?
A TLS handshake that times out leaves the connection open, a Niagara thread hangs, and Niagara has to be restarted manually to recover (per NVD and SB 2020-Tridium-2).
Which versions fix CVE-2020-14483?
Niagara 4.9.0.198 and Niagara Enterprise Security 4.9.0.60 (per SB 2020-Tridium-2 and CISA ICSA-20-224-03).
Why is the CVSS score of CVE-2020-14483 only 4.3?
NVD's vector requires an adjacent-network attacker (AV:A) and gives only a low availability impact, with no confidentiality or integrity impact (per NVD).
Does enabling FoxS protect against CVE-2020-14483?
No. The bug is in TLS handshake handling, and FoxS runs Fox over TLS on port 4911, so the fix is upgrading to Niagara 4.9 or later (per SB 2020-Tridium-2 and the Niagara 4 Hardening Guide).
Is CVE-2020-14483 exploited in the wild?
CISA's ICSA-20-224-03 says no known public exploits target it, it is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13), and FIRST EPSS gives it 0.0044, percentile 38.6, in the 2026-11-15 dataset (per CISA and FIRST EPSS).
Questions about this page?