"Update ntpkeygen/keygone to properly filter # characters. (CVE-2021-22212)"
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e448a0c3088ea0088b62f9b16debaccbba4d3334 commit e448a0c3088ea0088b62f9b16debaccbba4d3334 Author: Sam James <sam@gentoo.org> AuthorDate: 2021-06-11 06:38:52 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2021-06-11 06:38:52 +0000 net-misc/ntpsec: add 1.2.1 Bug: https://bugs.gentoo.org/795321 Signed-off-by: Sam James <sam@gentoo.org> net-misc/ntpsec/Manifest | 1 + net-misc/ntpsec/ntpsec-1.2.1.ebuild | 169 ++++++++++++++++++++++++++++++++++++ 2 files changed, 170 insertions(+)
arm64 done
amd64 done
arm done all arches done
Please cleanup
CVE-2021-22212: 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.
Unable to check for sanity: > no match for package: net-misc/ntpsec-1.2.1
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=155d768d81203eda2344e98b3c9510035cc4e778 commit 155d768d81203eda2344e98b3c9510035cc4e778 Author: Steve Arnold <nerdboy@gentoo.org> AuthorDate: 2021-12-02 22:09:48 +0000 Commit: Steve Arnold <nerdboy@gentoo.org> CommitDate: 2021-12-02 22:10:40 +0000 net-misc/ntpsec: Remove vulnerable 1.2.0 Bug: https://bugs.gentoo.org/795321 Package-Manager: Portage-3.0.20, Repoman-3.0.3 Signed-off-by: Steve Arnold <nerdboy@gentoo.org> net-misc/ntpsec/Manifest | 1 - net-misc/ntpsec/ntpsec-1.2.0-r3.ebuild | 169 --------------------------------- 2 files changed, 170 deletions(-)
