ntpd has Dependency on Vulnerable Third-Party Component

published 2023-08-24 3y ago modified 2024-06-26 2y ago

cvss: 2.6; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

During startup, an attacker that can man-in-the-middle traffic to and from NTS key exchange servers can trigger a very expensive key validation process due to a vulnerability in webpki.

### Impact This vulnerability can lead to excessive cpu usage on startup on clients configured to use NTS

### Patches Affected users are recommended to upgrade to version 0.3.7

### References See also https://github.com/rustsec/advisory-db/blob/main/crates/rustls-webpki/RUSTSEC-2023-0053.md

Patch / fix

fixed in 1 links 1

crates.io ntpd 0.3.7

github.com/pendulum-project/ntpd-rs@927952a commit

Is GHSA-37xq-q42p-rv3p in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by	version	score	vector
GitHub	3.1	2.6	CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L

Affected packages

ecosystem	package	affected	fixed in
crates.io	ntpd	<0.3.7	0.3.7

Classification

Weakness

CWE-1395 Dependency on Vulnerable Third-Party Component

References

Sources

GitHub Advisory GHSA-37xq-q42p-rv3p

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.