Search for packages
| purl | pkg:npm/jsrsasign@4.9.0 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-1va4-6h3w-h7an
Aliases: CVE-2022-25898 GHSA-3fvg-4v2m-98jf GMS-2022-2707 |
JWS and JWT signature validation vulnerability with special characters ### Impact Jsrsasign supports JWS(JSON Web Signatures) and JWT(JSON Web Token) validation. However JWS or JWT signature with non Base64URL encoding special characters or number escaped characters may be validated as valid by mistake. For example, even if a string of non Base64URL encoding characters such as `!@$%` or `\11` is inserted into a valid JWS or JWT signature value string, it will still be a valid JWS or JWT signature by mistake. When jsrsasign's JWS or JWT validation is used in OpenID connect or OAuth2, this vulnerability will affect to authentication or authorization. By our internal assessment, CVSS 3.1 score will be 8.6. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N ### Patches Users validate JWS or JWT signatures should upgrade to 10.5.25. ### Workarounds Validate JWS or JWT signature if it has Base64URL and dot safe string before executing JWS.verify() or JWS.verifyJWT() method. ### ACKNOWLEDGEMENT Thanks to Adi Malyanker and Or David for this vulnerability report. Also thanks for [Snyk security team](https://snyk.io/) for this coordination. ### References https://github.com/kjur/jsrsasign/releases/tag/10.5.25 https://github.com/kjur/jsrsasign/security/advisories/GHSA-3fvg-4v2m-98jf kjur's advisories https://github.com/advisories/GHSA-3fvg-4v2m-98jf github advisories https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25898 https://kjur.github.io/jsrsasign/api/symbols/KJUR.jws.JWS.html#.verifyJWT https://kjur.github.io/jsrsasign/api/symbols/KJUR.jws.JWS.html#.verify https://kjur.github.io/jsrsasign/api/symbols/global__.html#.isBase64URLDot https://github.com/kjur/jsrsasign/wiki/Tutorial-for-JWS-verification https://github.com/kjur/jsrsasign/wiki/Tutorial-for-JWT-verification https://security.snyk.io/vuln/SNYK-JS-JSRSASIGN-2869122 |
Affected by 7 other vulnerabilities. |
|
VCID-3c19-m13f-vbf1
Aliases: CVE-2021-30246 GHSA-27fj-mc8w-j9wg |
Improper Verification of Cryptographic Signature In the jsrsasign package for Node.js, some invalid RSA PKCS#1 v1.5 signatures are mistakenly recognized to be valid. NOTE: there is no known practical attack. |
Affected by 8 other vulnerabilities. |
|
VCID-b7u7-uwdr-vbgs
Aliases: CVE-2026-4601 GHSA-w8q8-93cx-6h7r |
jsrsasign: jsrsasign: Private Key Recovery via Missing Cryptographic Step in DSA Signing |
Affected by 0 other vulnerabilities. |
|
VCID-bgv2-wbuc-wqcj
Aliases: CVE-2026-4603 GHSA-464q-cqxq-xhgr |
jsrsasign: jsrsasign: Cryptographic operations impacted by division by zero via malicious JSON Web Key |
Affected by 0 other vulnerabilities. |
|
VCID-ddcm-ym8f-33hf
Aliases: CVE-2020-14968 GHSA-q3gh-5r98-j4h3 |
Improper Restriction of Operations within the Bounds of a Memory Buffer An issue was discovered in the jsrsasign package for Node.js. Its RSASSA-PSS (RSA-PSS) implementation does not detect signature manipulation/modification by prepending `\0` bytes to a signature (it accepts these modified signatures as valid). An attacker can abuse this behavior in an application by creating multiple valid signatures where only one signature should exist. Also, an attacker might prepend these bytes with the goal of triggering memory corruption issues. |
Affected by 12 other vulnerabilities. |
|
VCID-nu2y-1xy7-fff5
Aliases: CVE-2020-14966 GHSA-p8c3-7rj8-q963 |
Improper Verification of Cryptographic Signature An issue was discovered in the jsrsasign package for Node.js. It allows a malleability in ECDSA signatures by not checking overflows in the length of a sequence and `0` characters appended or prepended to an integer. The modified signatures are verified as valid. This could have a security-relevant impact if an application relied on a single canonical signature. |
Affected by 10 other vulnerabilities. |
|
VCID-q2dz-12f5-zbgg
Aliases: CVE-2026-4602 GHSA-8qwj-4jxw-m8jw |
jsrsasign: jsrsasign: Signature verification bypass via negative exponent handling |
Affected by 0 other vulnerabilities. |
|
VCID-qayx-46yz-d3b8
Aliases: CVE-2026-4598 GHSA-8g7p-jf3g-gxcp |
jsrsasign: jsrsasign: Denial of Service via infinite loop in bnModInverse function with crafted inputs |
Affected by 0 other vulnerabilities. |
|
VCID-r434-j4qg-r3bx
Aliases: CVE-2024-21484 GHSA-rh63-9qcf-83gf GMS-2024-46 |
Marvin Attack of RSA and RSAOAEP decryption in jsrsasign ### Impact RSA PKCS#1.5 or RSAOAEP ciphertexts may be decrypted by this Marvin attack vulnerability. ### Patches update to jsrsasign 11.0.0. ### Workarounds Find and replace RSA and RSAOAEP decryption with other crypto library. ### References https://people.redhat.com/~hkario/marvin/ https://github.com/kjur/jsrsasign/issues/598 |
Affected by 6 other vulnerabilities. |
|
VCID-sm4v-ac3f-6yha
Aliases: CVE-2026-4600 GHSA-wvqx-v3f6-w8rh |
jsrsasign: jsrsasign: Cryptographic signature forgery via malicious DSA domain parameters |
Affected by 0 other vulnerabilities. |
|
VCID-tqjx-apth-9qh1
Aliases: GHSA-h87q-g2wp-47pj GMS-2022-64 |
Signatures are mistakenly recognized to be valid in jsrsasign 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. |
Affected by 8 other vulnerabilities. |
|
VCID-xqn4-9ppe-qye1
Aliases: GHSA-g753-jx37-7xwh GMS-2020-741 |
ECDSA signature vulnerability of Minerva timing attack in jsrsasign ### Impact ECDSA side-channel attack named [Minerava](https://minerva.crocs.fi.muni.cz/) have been found and it was found that it affects to jsrsasign. Execution time of thousands signature generation have been observed then EC private key which is scalar value may be recovered since point and scalar multiplication time depends on bits of scalar. In jsrsasign 8.0.13 or later, execution time of EC point and scalar multiplication is almost constant and fixed for the issue. - Minerva is one of timing attack or side channel attack for EC. - If you don't use ECDSA class, you are not affected the vulnerability. - The vulnerability is that attacker may guess private key by checking processing time of EC key generation or ECDSA signing. - The cause issue is that point multiplication processing time in ECDSA signing is depends on private key value. - After 8.0.13, processing time of point multiplication in ECDSA signing have become constant for key value in theory. ### Patches Users using ECDSA signature generation should upgrade to 8.0.13 or later. ### Workarounds There is no workarounds in jsrsasign. Update jsrsasign or use other ECDSA library. ### ACKNOWLEDGEMENT Thanks to Jan Jancar @J08nY, Petr Svenda and Vladimir Sedlacek of Masaryk University in Czech Republic to find and report this vulnerability. ### References https://minerva.crocs.fi.muni.cz/ https://www.npmjs.com/advisories/1505 https://github.com/kjur/jsrsasign/issues/411 |
Affected by 13 other vulnerabilities. |
|
VCID-y36k-rayk-dyh8
Aliases: CVE-2020-14967 GHSA-xxxq-chmp-67g4 |
Improper Restriction of Operations within the Bounds of a Memory Buffer An issue was discovered in the jsrsasign package for Node.js. Its RSA PKCS1 v1.5 decryption implementation does not detect ciphertext modification by prepending `\0` bytes to ciphertexts (it decrypts modified ciphertexts without error). An attacker might prepend these bytes with the goal of triggering memory corruption issues. |
Affected by 11 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||