First published: Tue Jun 08 2021(Updated: )
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.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
NTPsec | =1.2.0 | |
Fedora | =34 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-22212 has a medium severity rating due to potential mismanagement of keys in NTPsec.
To fix CVE-2021-22212, users should avoid using '#' characters in keys generated by ntpkeygen.
CVE-2021-22212 affects NTPsec version 1.2.0.
Administrators may find that keys created with '#' characters are either improperly loaded or unusable, leading to potential service disruption.
Yes, CVE-2021-22212 impacts Fedora 34 due to its use of the affected NTPsec version.