"Update ntpkeygen/keygone to properly filter # characters. (CVE-2021-22212)"
The bug has been referenced in the following commit(s):
Author: Sam James <email@example.com>
AuthorDate: 2021-06-11 06:38:52 +0000
Commit: Sam James <firstname.lastname@example.org>
CommitDate: 2021-06-11 06:38:52 +0000
net-misc/ntpsec: add 1.2.1
Signed-off-by: Sam James <email@example.com>
net-misc/ntpsec/Manifest | 1 +
net-misc/ntpsec/ntpsec-1.2.1.ebuild | 169 ++++++++++++++++++++++++++++++++++++
2 files changed, 170 insertions(+)
all arches done
ntpkeygen can generate keys that ntpd fails to parse. NTPsec 1.2.0 allows ntpkeygen to generate keys with '#' characters. ntpd then either pads, shortens the key, or fails to load these keys entirely, depending on the key type and the placement of the '#'. This results in the administrator not being able to use the keys as expected or the keys are shorter than expected and easier to brute-force, possibly resulting in MITM attacks between ntp clients and ntp servers. For short AES128 keys, ntpd generates a warning that it is padding them.