CVE-2013-5211 is the ntpd monlist amplification flaw: ntpd before 4.2.7p26 answers a small forged REQ_MON_GETLIST request with a far larger reply, so any device that serves NTP to the internet can be used to flood a victim. It was exploited in the wild in December 2013, and EPSS still rates it 0.975.
Vulnerability summary
CVSS base score
5
Medium severity
EPSS score (FIRST)
97.5%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2013-5211 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| NTP reference implementation (ntp.org ntpd) | cpe:2.3:a:ntp:ntp:*:*:*:*:*:*:*:* | before 4.2.7p26 (fixed in 4.2.7p26, 2010-04-24); mitigated by noquery or disable monitor |
| Hitachi Energy TropOS devices series 1400/2400/6400 | — | all versions before 8.9.6 (per CISA ICS Advisory ICSA-24-352-02) |
What does this mean for affected devices?
CVE-2013-5211 is a traffic amplification flaw in the NTP reference implementation. NVD describes the monlist feature in ntp_request.c in ntpd before 4.2.7p26 as allowing remote attackers to cause a denial of service "via forged (1) REQ_MON_GETLIST or (2) REQ_MON_GETLIST_1 requests, as exploited in the wild in December 2013". NVD scores it CVSS v2 5.0 (AV:N/AC:L/Au:N/C:N/I:N/A:P) under CWE-20 and has no v3 score for it. CERT/CC's VU#348126 classifies the same issue as CWE-406, network amplification, and measures the bandwidth amplification factor of the two monlist requests at "up to 3660 and 5500 respectively". The device that answers is not the victim; it becomes the weapon.
The fix is old. ntp.org's notice for bug 1532 says the flaw is resolved in 4.2.7p26, publicly released on 2010-04-24, and that users of earlier versions should either use noquery in their default restrictions or disable monitor. It is still a firmware problem because devices with old ntpd builds stay deployed. CISA published ICS advisory ICSA-14-051-04 in February 2014 for the control-system community, listing NTP 4.2.7p25 and earlier with monlist support as affected. Ten years later, CISA's ICSA-24-352-02 of 2024-12-17 names a product: Hitachi Energy TropOS devices series 1400/2400/6400, all versions before 8.9.6, scored CVSS v3 5.3, with the vendor recommending an update to 8.9.6 or later when available, plus firewall rules and filters against DoS. CERT/CC lists Cisco, Hewlett-Packard, Meinberg Funkuhren and NEC as affected vendors.
For a device maker, the questions are which NTP implementation the image ships and whether it answers queries from outside. Our NTP and chrony vulnerabilities guide shows how to tell ntp.org ntpd from NTPsec, chrony and BusyBox ntpd in an unpacked image and gives the restrict default ... noquery baseline from RFC 8633. The Debian security tracker notes that the default configuration is safe and the issue is "mitigated if noquery used", which is why the check has to look at ntp.conf and not only at the version string. A device that only needs to be a client should drop inbound UDP 123 on its WAN interface. When a product is not affected because ntpd is absent or restricted, record that in a VEX statement, as our CSAF and VEX for device makers guide explains.
Despite the in-the-wild exploitation NVD records, the CVE is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.97549 (99.9th percentile) in its 2026-11-15 dataset, which reflects that scanning for open monlist responders has never stopped. A related BusyBox time-server flaw, CVE-2016-6301, shows the same pattern of a time daemon answering packets it should ignore.
Evidence
- monlist in ntpd before 4.2.7p26 allows traffic amplification via forged REQ_MON_GETLIST/REQ_MON_GETLIST_1 requests, exploited in the wild in December 2013; CVSS v2 5.0; CWE-20. — NVD
- Resolved in 4.2.7p26 (public release 2010-04-24); mitigate with noquery or disable monitor. — ntp.org bug 1532
- Amplification factor up to 3660 (REQ_MON_GETLIST) and 5500 (REQ_MON_GETLIST_1); CWE-406; Cisco, Hewlett-Packard, Meinberg Funkuhren and NEC listed as affected. — CERT/CC VU#348126
- NTP 4.2.7p25 and prior with monlist support affected; upgrade to 4.2.7p26 or later. — CISA ICSA-14-051-04
- Hitachi Energy TropOS devices series 1400/2400/6400 before 8.9.6 affected; CVSS v3 5.3; update to 8.9.6 or later when available. — CISA ICSA-24-352-02
- Not in the CISA KEV catalog version 2026.11.13 (checked 2026-11-16). — CISA KEV
- EPSS 0.97549, 99.9th percentile, FIRST dataset of 2026-11-15. — FIRST EPSS

Related advisories
Sources
- NVD: CVE-2013-5211
- ntp.org: NTP Bug 1532 (CVE-2013-5211)
- CERT/CC VU#348126: NTP can be abused to amplify denial-of-service attack traffic
- CISA ICS Advisory ICSA-14-051-04: NTP Reflection Attack
- CISA ICS Advisory ICSA-24-352-02: Hitachi Energy TropOS Devices Series 1400/2400/6400
- Debian Security Tracker: CVE-2013-5211
- CISA KEV catalog
- FIRST EPSS
Frequently asked questions
Why does a 2013 NTP flaw still matter for firmware?
Because devices with old ntpd builds remain in service. CISA published ICSA-24-352-02 on 2024-12-17 for Hitachi Energy TropOS devices series 1400/2400/6400 before 8.9.6, more than a decade after the fix in ntpd 4.2.7p26 (per CISA and ntp.org).
How much traffic can monlist amplify?
CERT/CC measured bandwidth amplification factors of up to 3660 for REQ_MON_GETLIST and 5500 for REQ_MON_GETLIST_1, comparing the reply payload with the request payload (per CERT/CC VU#348126).
How do you mitigate CVE-2013-5211 without upgrading ntpd?
ntp.org advises noquery in the default restrictions, which blocks all status queries, or disable monitor, which turns off monlist only. On a device that is only a time client, also drop inbound UDP 123 on WAN interfaces (per ntp.org bug 1532).
Is CVE-2013-5211 in the CISA KEV catalog?
No. Although NVD's description records exploitation in the wild in December 2013, the CVE is not in CISA KEV catalog version 2026.11.13 (checked 2026-11-16). FIRST EPSS gives it 0.97549 in its 2026-11-15 dataset (per NVD, CISA KEV and FIRST EPSS).
Questions about this page?