Signatures are mistakenly recognized to be valid in jsrsasign
Priority LOW 38CWE-347Published · 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-347.
Summary
In the jsrsasign package through 10.1.13 for Node.js, some invalid RSA PKCS#1 v1.5 signatures are mistakenly recognized to be valid. NOTE: there is no known practical attack.
Why it matters now
Fix Fixed jsrsasign (npm): 10.2.0
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 |
|---|---|---|---|---|---|
| — | jsrsasign (npm) | before 10.2.0 | 10.2.0 | Patch available | GHSA-h87q-g2wp-47pj |
- jsrsasign (npm) Vendor— Affected before 10.2.0 Fixed in 10.2.0 Patch available GHSA-h87q-g2wp-47pj
Remediation
- Fix · GHSA-h87q-g2wp-47pj jsrsasign (npm) Fixed in 10.2.0 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-h87q-g2wp-47pj
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences