Use of a Risky Cryptographic Algorithm Affecting ntpsec/ntpsec package, versions [0,]


Severity

Recommended
0.0
high
0
10

CVSS assessment by Snyk's Security Team. 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 Learn

Learn about Use of a Risky Cryptographic Algorithm vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-UNMANAGED-NTPSECNTPSEC-2365355
  • published26 Jan 2022
  • disclosed8 Jun 2021
  • creditUnknown

Introduced: 8 Jun 2021

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

How to fix?

There is no fixed version for ntpsec/ntpsec.

Overview

Affected versions of this package are vulnerable to Use of a Risky Cryptographic Algorithm 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