CVE-2016-1548
CVE-2016-1548 Vulnerability Analysis & Exploit Intelligence
An attacker can spoof a packet from a legitimate ntpd server with an origin timestamp that matches the peer->dst timestamp recorded for that server. After making this switch, the client in NTP 4.2.8p4 and earlier and NTPSec aa48d001683e5b791a743ec9c575aaf7d867a2b0c will reject all future legitimate server responses. It is possible to force the victim client to move time after the mode has been changed. ntpq gives no indication that the mode has been switched.
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
4%
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
25 on the record
- www.ubuntu.com/usn/USN-3096-1
vendor-advisory, x_refsource_UBUNTU
- www.debian.org/security/2016/dsa-3629
vendor-advisory, x_refsource_DEBIAN
- www.talosintelligence.com/reports/TALOS-2016-0082/
x_refsource_MISC
- www.oracle.com/technetwork/topics/security/linuxbulletinapr2016-2952096.html
x_refsource_CONFIRM
- access.redhat.com/errata/RHSA-2016:1141
vendor-advisory, x_refsource_REDHAT
- lists.opensuse.org/opensuse-security-announce/2016-07/msg00026.html
vendor-advisory, x_refsource_SUSE
- www.securityfocus.com/bid/88264
vdb-entry, x_refsource_BID
- www.kb.cert.org/vuls/id/718152
third-party-advisory, x_refsource_CERT-VN
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.