Improper Key Verification in ipns

published 2019-05-30 7y ago modified 2023-12-07 2y ago

cvss: 7.5; 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

Versions 0.1.1 or 0.1.2 of `ipns` are vulnerable to improper key validation. This is due to the public key verification was not being performed properly, resulting in any key being valid.

## Recommendation

Update to version 0.1.3 or later.

Patch / fix

fixed in 1 links 1

npm ipns 0.1.3

github.com/ipfs/js-ipns@33684e3 commit

Is GHSA-j59f-6m4q-62h6 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	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	ipns	<0.1.3	0.1.3

Classification

Weakness

CWE-287 Improper Authentication

References

Sources

GitHub Advisory GHSA-j59f-6m4q-62h6

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.