CVE-2016-1551
CVE-2016-1551 Vulnerability Analysis & Exploit Intelligence
ntpd in NTP 4.2.8p3 and NTPsec a5fb34b9cc89b92a8fef2f459004865c93bb7f92 relies on the underlying operating system to protect it from requests that impersonate reference clocks. Because reference clocks are treated like other peers and stored in the same structure, any packet with a source ip address of a reference clock (127.127.1.1 for example) that reaches the receive() function will match that reference clock's peer record and will be treated as a trusted peer. Any system that lacks the typical martian packet filtering which would block these packets is in danger of having its time controlled by an attacker.
Published Updated Sources: cvelistV5, certcc
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
2%
chance of exploitation in 30 days
CVSS base
Unscored
no source published a base score
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (2)
Products (2)
References
7 on the record
- www.securityfocus.com/bid/88219
vdb-entry, x_refsource_BID
- www.talosintelligence.com/reports/TALOS-2016-0132/
x_refsource_MISC
- www.securitytracker.com/id/1035705
vdb-entry, x_refsource_SECTRACK
- www.oracle.com/technetwork/topics/security/bulletinapr2016-2952098.html
x_refsource_CONFIRM
- security.netapp.com/advisory/ntap-20171004-0002/
x_refsource_CONFIRM
- security.FreeBSD.org/advisories/FreeBSD-SA-16:16.ntp.asc
vendor-advisory, x_refsource_FREEBSD
- security.gentoo.org/glsa/201607-15
vendor-advisory, x_refsource_GENTOO
Elsewhere on this site
- ntp projectevery CVE for this vendor
- ntpsec projectevery CVE for this vendor
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.