CVE-2015-7704
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe ntpd client in NTP 4.x before 4.2.8p4 and 4.3.x before 4.3.77 allows remote attackers to cause a denial of service via a number of crafted "KOD" messages.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe ntpd client in NTP versions 4.x before 4.2.8p4 and 4.3.x before 4.3.77 is vulnerable to remote denial of service via specially crafted Kiss-of-Death (KOD) messages. When an attacker sends multiple malicious KOD packets to a vulnerable NTP client, it can cause the service to become unresponsive or crash.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 7.0= 8.0= 9.0= 6.0= 7.0= 6.0= 7.0= 6.5= 6.6= 7.3= 7.4= 7.6= 7.7= 6.5= 6.6= 6.7= 7.1= 7.3= 7.4= 7.5= 7.6= 7.7= 6.5= 6.6= 7.3= 7.6= 7.7= 6.0= 7.0= 6.0.2= 6.2.0= 6.5= 7.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm NTP daemon is runningRun 'systemctl status ntpd' on RHEL/CentOS, 'systemctl status ntp' on Debian, or 'ps aux | grep ntpd' to verify the ntpd process is activeAffected if If ntpd is running, the system could be affected by this vulnerability
-
Identify installed NTP versionRun 'ntpd --version' or 'ntpq --version' to get the exact version number of the NTP installationAffected if Version is 4.x before 4.2.8p4 OR 4.3.x before 4.3.77 - compare your output to these thresholds
-
Verify NTP is listening on networkRun 'netstat -anup | grep :123' or 'ss -anup | grep :123' to confirm ntpd is bound to UDP port 123Affected if If ntpd is bound to accessible network interfaces, it can receive malicious KOD packets from attackers
-
Check KOD processing configurationExamine /etc/ntp.conf for 'kod' or 'limited' directives in the restrict lines, or run 'ntpq -c rl' to query rate limiting settingsAffected if If KOD processing is enabled and ntpd is network-accessible, the vulnerability can be triggered
-
Confirm NTP is exposed to untrusted networksReview firewall rules with 'iptables -L -n' or 'firewall-cmd --list-all' to determine if UDP port 123 is open to untrusted sourcesAffected if If UDP port 123 is accessible from outside trusted networks, remote attackers can send malicious KOD packets
A system is affected if it runs a vulnerable NTP version (before 4.2.8p4 or 4.3.77) with ntpd listening on accessible network interfaces and KOD processing enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade NTP to version 4.2.8p4, 4.3.77, or later to patch this vulnerability. Alternatively, implement network-level filtering to restrict NTP traffic to trusted sources.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7704 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sources- bugs.ntp.org
- support.ntp.org
- support.ntp.org
- rhn.redhat.com
- rhn.redhat.com
- www.debian.org
- www.oracle.com
- www.securityfocus.com
- www.securitytracker.com
- bugzilla.redhat.com
- h20566.www2.hpe.com
- kc.mcafee.com
- security.gentoo.org
- security.netapp.com
- security.netapp.com
- support.citrix.com
- www.cs.bu.edu
- www.kb.cert.org
- eprint.iacr.org
- www.arista.com
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-7704 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data