chrony: packet modification
| Package(s): | chrony | CVE #(s): | CVE-2016-1567 | ||||||||||||||||||||
| Created: | January 25, 2016 | Updated: | December 14, 2016 | ||||||||||||||||||||
| Description: | From the Red Hat bugzilla:
The following flaw was found in chrony: Symmetric key encryption requires a single trusted key to be specified for each server configuration. A key specified only for one server should only work to authenticate that server, other trusted keys should be refused. However, when symmetric key authentication is verified, there is no check that the key used is the key specified for the address, any trusted key can be used as long as the keyid references another key the systems share and that key is used to compute the MAC. An authenticated client (A) could use this flaw to modify a packet sent between a server (B) and a client (C) using a key that is different from the one known to the client (A). | ||||||||||||||||||||||
| Alerts: |
| ||||||||||||||||||||||