Use of a Broken or Risky Cryptographic Algorithm Affecting ntpsec package, versions <1.2.0+dfsg1-4


Severity

Recommended
0.0
high
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.52% (40th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ECHOLATEST-NTPSEC-18496111
  • published1 Aug 2026
  • disclosed8 Jun 2021

Introduced: 8 Jun 2021

CVE-2021-22212  (opens in a new tab)
CWE-327  (opens in a new tab)

How to fix?

Upgrade Echo:latest ntpsec to version 1.2.0+dfsg1-4 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream ntpsec package and not the ntpsec package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1