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.
The product uses a broken or risky cryptographic algorithm or protocol.
Link | Tags |
---|---|
https://gitlab.com/NTPsec/ntpsec/-/issues/699 | issue tracking third party advisory patch |
https://bugzilla.redhat.com/show_bug.cgi?id=1955859 | issue tracking third party advisory patch |
https://gitlab.com/gitlab-org/cves/-/blob/master/2021/CVE-2021-22212.json | third party advisory |
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/3GIT2HYL5BQXPGKI6ZDNG473IEQ5WQF2/ | vendor advisory |