ubuntu-cve-2021-22212
Vulnerability from osv_ubuntu
Published
2021-06-08 13:15
Modified
2025-03-24 04:40
Summary
Details

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.

Severity
7.4 (High)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
References
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {
        "ubuntu_priority": "low"
      },
      "package": {
        "ecosystem": "Ubuntu:Pro:18.04:LTS",
        "name": "ntpsec",
        "purl": "pkg:deb/ubuntu/ntpsec@1.1.0+dfsg1-1ubuntu0.2?arch=source\u0026distro=esm-apps/bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "1.0.0+dfsg1-1",
        "1.0.0+dfsg1-3",
        "1.1.0+dfsg1-1",
        "1.1.0+dfsg1-1ubuntu0.1",
        "1.1.0+dfsg1-1ubuntu0.2"
      ]
    },
    {
      "ecosystem_specific": {
        "ubuntu_priority": "low"
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "ntpsec",
        "purl": "pkg:deb/ubuntu/ntpsec@1.1.8+dfsg1-4build1?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "1.1.3+dfsg1-2",
        "1.1.7+dfsg1-1",
        "1.1.7+dfsg1-2",
        "1.1.8+dfsg1-1",
        "1.1.8+dfsg1-3",
        "1.1.8+dfsg1-4",
        "1.1.8+dfsg1-4build1"
      ]
    }
  ],
  "aliases": [],
  "details": "ntpkeygen can generate keys that ntpd fails to parse. NTPsec 1.2.0 allows ntpkeygen to generate keys with \u0027#\u0027 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 \u0027#\u0027. 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.",
  "id": "UBUNTU-CVE-2021-22212",
  "modified": "2025-03-24T04:40:23Z",
  "published": "2021-06-08T13:15:00Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2021-22212"
    },
    {
      "type": "REPORT",
      "url": "https://gitlab.com/NTPsec/ntpsec/-/issues/699"
    },
    {
      "type": "REPORT",
      "url": "https://gitlab.com/gitlab-org/cves/-/blob/master/2021/CVE-2021-22212.json"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/show_bug.cgi?id=1955859"
    },
    {
      "type": "REPORT",
      "url": "https://www.cve.org/CVERecord?id=CVE-2021-22212"
    }
  ],
  "related": [
    "CVE-2021-22212"
  ],
  "schema_version": "1.6.3",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
      "type": "CVSS_V3"
    }
  ],
  "withdrawn": "2025-06-23T15:53:58Z"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.