Improper Key Verification in ipns
Priority LOW 38CWE-287Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-287.
Summary
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.
Why it matters now
Fix Fixed ipns (npm): 0.1.3
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | ipns (npm) | before 0.1.3 | 0.1.3 | Patch available | GHSA-j59f-6m4q-62h6 |
- ipns (npm) Vendor— Affected before 0.1.3 Fixed in 0.1.3 Patch available GHSA-j59f-6m4q-62h6
Remediation
- Fix · GHSA-j59f-6m4q-62h6 ipns (npm) Fixed in 0.1.3 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-j59f-6m4q-62h6
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences