How severe is CVE-2013-5211?

No CVSS score has been assigned to CVE-2013-5211 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-5211?

Affected package information for CVE-2013-5211 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2013-5211?

No fixed release is recorded for CVE-2013-5211 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2013-5211 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2013-5211 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2013-5211 actively exploited in the wild?

Yes. There are 19 known exploit references for CVE-2013-5211, including 1 documented proof-of-concept exploit on Exploit-DB and 15 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2013-5211?

CVE-2013-5211 has an EPSS (Exploit Prediction Scoring System) score of 97.5%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2013-5211?

CVE-2013-5211 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-5211 published, and has it been updated?

CVE-2013-5211 was published on January 2, 2014 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2013-5211 — Oracle

CVE-2013-5211 is a Improper Input Validation vulnerability. 19 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Published

Jan 2, 2014

Updated

Apr 16, 2026

Affected

3 products

Patched

See advisory

Exploits

19 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

97.5%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

The monlist feature in ntp_request.c in ntpd in NTP before 4.2.7p26 allows remote attackers to cause a denial of service (traffic amplification) via forged (1) REQ_MON_GETLIST or (2) REQ_MON_GETLIST_1 requests, as exploited in the wild in December 2013.

Affected Products

3 products · 31 configurations

Application

ntpntp

< 4.2.7

1 version

4.2.7

opensuseopensuse

1 version

11.4

linuxoracle

2 versions

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-33073doslinux

NTP ntpd monlist Query Reflection - Denial of Service

by Danilo PC · Apr 28, 2014

Exploit-DB Source

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2013-5211 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-5211 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works