CVE-2020-11868 is a flaw in ntpd from ntp before 4.2.8p14 (and 4.3.x before 4.3.100): an off-path attacker can stop a client from synchronizing by sending a server mode packet with a spoofed source address. NVD scores it 7.5, MITRE 5.9. Belden lists Hirschmann HiSecOS EAGLE firewalls 3.5.0 to 4.2.02 as affected, fixed in HiSecOS 04.3.00.
Vulnerability summary
CVSS base score
7.5
High severity
EPSS score (FIRST)
2.1%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2020-11868 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| ntp (ntpd) | cpe:2.3:a:ntp:ntp:*:*:*:*:*:*:*:* | before 4.2.8p14, and 4.3.x before 4.3.100 (fixed in 4.2.8p14 and 4.3.100) |
| Hirschmann HiSecOS EAGLE firewalls | — | 3.5.0 to 4.2.02; fixed in 04.3.00 (Belden BSECV-2021-15) |
What does this mean for affected devices?
NVD's description: "ntpd in ntp before 4.2.8p14 and 4.3.x before 4.3.100 allows an off-path attacker to block unauthenticated synchronization via a server mode packet with a spoofed source IP address, because transmissions are rescheduled even when a packet lacks a valid origin timestamp." NVD's Primary score is CVSS v3.1 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) with CWE-346 (origin validation error). The CNA, MITRE, scored it lower at CVSS v3.0 5.9 with high attack complexity; the CISA ADP entry matches NVD at 7.5 (NVD, CVE record). The NTP project tracks it as bug 3592, "DoS attack on client ntpd".
What happens to a device that hits this bug?
An attacker who is not on the path between client and server sends the client a server mode packet with the real server's address forged as the source. Because ntpd reschedules its transmissions even when the packet has no valid origin timestamp, the attacker can keep the client from synchronizing with that server. The attack works against unauthenticated NTP, which is the usual setup on embedded devices. Clocks that drift break log correlation, certificate checks and time-stamped process data.
Which Hirschmann products are affected?
Belden bulletin BSECV-2021-15 (2023-07-25) lists Hirschmann HiSecOS EAGLE firewalls from 3.5.0 to 4.2.02 as affected by this CVE and three other NTP flaws: CVE-2020-15025, CVE-2020-13817 and CVE-2018-8956. The fix is HiSecOS 04.3.00. Belden's mitigation is to configure only trusted NTP servers and ensure that an attacker cannot inject spoofed NTP packets into the network (Belden BSECV-2021-15). Belden quotes 7.5 for this CVE, the NVD figure.
What fixes it in the ntp package?
Upstream fixed it in ntp 4.2.8p14 and 4.3.100. Distributions backported or shipped the fix at different speeds: the Debian tracker lists ntp fixed in unstable in 1:4.2.8p14+dfsg-1 and in jessie by DLA-2201-1, marks buster and stretch as a minor issue without a DSA, and records ntpsec as not affected per upstream. A firmware image is only fixed when its ntpd build carries the change, so check the ntpd version string inside the image, not the vendor release notes alone.
The Hirschmann and Belden switch vulnerability guide lists BSECV-2021-15 with the other third-party bulletins, and our NTP and chrony guide covers time sync daemons in firmware. CVE-2013-5211 is the older ntpd monlist amplification flaw, and CVE-2021-43523 is another third-party library flaw in Hirschmann firewall firmware.
CVE-2020-11868 is not in the CISA KEV catalog as of 2026-11-21 (catalog version 2026.11.20, 1,790 entries). FIRST EPSS gives it 0.02116, the 82.3rd percentile, in the 2026-11-20 dataset (CISA KEV, FIRST EPSS).
Evidence
- NVD (read 2026-11-21): status Modified; published 2020-04-17; NVD Primary CVSS v3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, v2 5.0; CNA ([email protected]) Secondary CVSS v3.0 5.9 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H; CISA ADP Secondary 7.5; CWE-346; CPEs ntp up to 4.2.7, 4.2.8 through p13, 4.3.98 to before 4.3.100; references NTP bug 3592. — NVD
- Belden BSECV-2021-15 version 1.0 (2023-07-25), read 2026-11-21: CVE-2020-15025 (4.9), CVE-2020-13817 (7.4), CVE-2020-11868 (7.5), CVE-2018-8956 (5.3) affect Hirschmann HiSecOS EAGLE 3.5.0 to 4.2.02; solution HiSecOS EAGLE 04.3.00; mitigation configure only trusted NTP servers and ensure an attacker cannot inject spoofed NTP packets. — Belden BSECV-2021-15
- Debian security tracker, read 2026-11-21: ntp fixed in unstable 1:4.2.8p14+dfsg-1, jessie 1:4.2.6.p5+dfsg-7+deb8u3 (DLA-2201-1); buster and stretch no-dsa (minor issue); ntpsec not affected per upstream; references NTP bug 3592. — Debian security tracker
- CVE record (checked 2026-11-21): state PUBLISHED, CNA MITRE, published 2020-04-17; CNA CVSS v3.0 5.9; CISA-ADP CVSS v3.1 entry. — CVE.org
- Not in the CISA KEV catalog, version 2026.11.20 (1,790 entries), checked 2026-11-21. — CISA KEV
- EPSS 0.02116, percentile 0.82286, dataset 2026-11-20, read 2026-11-21. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Which Hirschmann products does CVE-2020-11868 affect?
Belden BSECV-2021-15 lists Hirschmann HiSecOS EAGLE firewalls from 3.5.0 to 4.2.02 and names HiSecOS 04.3.00 as the fix, together with three other NTP CVEs.
Which ntp version fixes it?
NVD names ntp before 4.2.8p14 and 4.3.x before 4.3.100 as affected, so 4.2.8p14 and 4.3.100 carry the fix. Debian records ntpsec as not affected per upstream.
What can I do if I cannot update yet?
Belden's mitigation is to configure only trusted NTP servers and make sure an attacker cannot inject spoofed NTP packets into the network, for example by filtering NTP at the network edge.
Why do NVD and MITRE give different scores?
MITRE, the CNA, rated attack complexity high (5.9); NVD rated it low (7.5), and the CISA ADP entry and Belden's bulletin also use 7.5. Both describe an availability impact only.
Is CVE-2020-11868 exploited?
It is not in the CISA KEV catalog as of 2026-11-21 (version 2026.11.20). FIRST EPSS gives it 0.02116, the 82.3rd percentile, in the 2026-11-20 dataset.
Questions about this page?