NTPsec 1.2.0
Approved changes feed: RSS · Atom
cpe:2.3:a:ntpsec:ntpsec:1.2.0:*:*:*:*:*:*:*
part: a version: 1.2.0 update: *
| Vendor | Ntpsec (c7e54110-3f4d-5834-80af-76a04baa27a4) |
|---|---|
| Product | Ntpsec (3147871e-e611-5dde-9369-37c846d2a777) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:bitbucket/ntpsec/ntpsec |
purl2cpe | 2026-06-01 10:15:00.830636 |
pkg:deb/debian/ntpsec |
purl2cpe | 2026-06-01 10:15:00.830637 |
pkg:deb/ubuntu/ntpsec |
purl2cpe | 2026-06-01 10:15:00.830638 |
pkg:github/ntpsec/ntpsec |
purl2cpe | 2026-06-01 10:15:00.830640 |
pkg:rpm/fedora/ntpsec |
purl2cpe | 2026-06-01 10:15:00.830641 |
pkg:rpm/opensuse/ntpsec |
purl2cpe | 2026-06-01 10:15:00.830642 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2021-22212 |
vulnerable | 2026-06-08 05:30:00.016560 |
Details available
MEDIUM (4)
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.
Published: 2021-06-08T12:07:02.000Z
Updated: 2024-08-03T18:37:18.446Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.