CVE-2024-21484
https://notcve.org/view.php?id=CVE-2024-21484
Versions of the package jsrsasign before 11.0.0 are vulnerable to Observable Discrepancy via the RSA PKCS1.5 or RSAOAEP decryption process. An attacker can decrypt ciphertexts by exploiting the Marvin security flaw. Exploiting this vulnerability requires the attacker to have access to a large number of ciphertexts encrypted with the same key. Workaround The vulnerability can be mitigated by finding and replacing RSA and RSAOAEP decryption with another crypto library. Las versiones del paquete jsrsasign anteriores a 11.0.0 son vulnerables a la discrepancia observable a través del proceso de descifrado RSA PKCS1.5 o RSAOAEP. • https://github.com/kjur/jsrsasign/issues/598 https://github.com/kjur/jsrsasign/releases/tag/11.0.0 https://people.redhat.com/~hkario/marvin https://security.snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-6070734 https://security.snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWERGITHUBKJUR-6070733 https://security.snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-6070732 https://security.snyk.io/vuln/SNYK-JS-JSRSASIGN-6070731 • CWE-203: Observable Discrepancy •
CVE-2022-25898 – Improper Verification of Cryptographic Signature
https://notcve.org/view.php?id=CVE-2022-25898
The package jsrsasign before 10.5.25 are vulnerable to Improper Verification of Cryptographic Signature when JWS or JWT signature with non Base64URL encoding special characters or number escaped characters may be validated as valid by mistake. Workaround: Validate JWS or JWT signature if it has Base64URL and dot safe string before executing JWS.verify() or JWS.verifyJWT() method. El paquete jsrsasign versiones anteriores a 10.5.25, es vulnerable a una Verificación Inapropiada de la Firma Criptográfica cuando la firma JWS o JWT con caracteres especiales de codificación no Base64URL o con caracteres de escape de número puede ser comprobada como válida por error. Mitigación: Comprobar la firma JWS o JWT si presenta Base64URL y cadena de puntos segura antes de ejecutar el método JWS.verify() o JWS.verifyJWT() • https://github.com/kjur/jsrsasign/commit/4536a6e9e8bcf1a644ab7c07ed96e453347dae41 https://github.com/kjur/jsrsasign/releases/tag/10.5.25 https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-2935898 https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWERGITHUBKJUR-2935897 https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-2935896 https://snyk.io/vuln/SNYK-JS-JSRSASIGN-2869122 • CWE-347: Improper Verification of Cryptographic Signature •
CVE-2021-30246
https://notcve.org/view.php?id=CVE-2021-30246
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. En el paquete jsrsasign versiones hasta 10.1.13 para Node.js, algunas firmas RSA PKCS#1 v1.5, firmas son erróneamente reconocidas como válidas. NOTA: No es conocido un ataque práctico • https://github.com/kjur/jsrsasign/issues/478 https://github.com/kjur/jsrsasign/releases/tag/10.1.13 https://kjur.github.io/jsrsasign • CWE-347: Improper Verification of Cryptographic Signature •
CVE-2020-14966
https://notcve.org/view.php?id=CVE-2020-14966
An issue was discovered in the jsrsasign package through 8.0.18 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. Se detectó un problema en el paquete jsrsasign por medio de 8.0.18 para Node.js. • https://github.com/kjur/jsrsasign/issues/437 https://github.com/kjur/jsrsasign/releases/tag/8.0.17 https://github.com/kjur/jsrsasign/releases/tag/8.0.18 https://kjur.github.io/jsrsasign https://security.netapp.com/advisory/ntap-20200724-0001 https://www.npmjs.com/package/jsrsasign • CWE-347: Improper Verification of Cryptographic Signature •
CVE-2020-14968
https://notcve.org/view.php?id=CVE-2020-14968
An issue was discovered in the jsrsasign package before 8.0.17 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. Se detectó un problema en el paquete jsrsasign versiones anteriores a 8.0.17 para Node.js. • https://github.com/kjur/jsrsasign/issues/438 https://github.com/kjur/jsrsasign/releases/tag/8.0.17 https://github.com/kjur/jsrsasign/releases/tag/8.0.18 https://kjur.github.io/jsrsasign https://security.netapp.com/advisory/ntap-20200724-0001 https://www.npmjs.com/package/jsrsasign • CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer •